Topic: Development
Building Viget.com In EE (Part 2)
In my last EE post, I covered some ExpressionEngine tricks we used for managing multiple sites, removing the /comments URL segment, and setting up a simple “Preview” function.
This time, we’re going to use URL segments to create some dynamic user profiles, sort a portfolio page, and make a flexible upcoming event list.
Pulling Your Flickr Feed with jQuery
Feeds are the easiest way to view updated content, whether it's through a feed reader or outputted onto a web site. There are many different types of feeds, such as RSS or Atom, and many different ways display them on your site, such as using MagpieRSS to parse an RSS feed in PHP. However, you can also display feeds on your site using JavaScript, so in this post I'm going to be talking about a feed format called JSON and how you can use JavaScript to parse it out and display it.
JSON (JavaScript Object Notation) is a data format that is easy to read and language-independent, meaning you can parse it using any programming language. Both Yahoo! and Google have been offering data from their sites in JSON format for the past couple years. A good example of this is Flickr. Anyone with a Flickr account can access a JSON feed of their photos.
Finding Your Feed
If we go to the Viget Inspire collection on Flickr, we can click on the feed (orange button, bottom of the page) and bring up a RSS 2.0 feed of all the images in our pool. Flickr's API has many other feed formats, so I suggest going to their site to read up on it because there are a lot of things you can do. If you want the JSON version of the feed, change "format=rss_200" at the end of the query string to "format=json" so that your URL looks like this:
Building Viget.com In EE (Part 1)
When we decided on the new strategy for Viget.com, a few technology options were considered for the relaunch. We needed a platform that:
- Could accommodate the types of content (five blogs, five blogrolls, Flickr feeds, team member pages, work pages, careers) we wanted to add to the site
- A designer could build without in-depth programming knowledge
- Allowed us to manage the structure of the four sub-blogs
ExpressionEngine was the clear choice, with powerful customization options and a great community behind the scenes. Still, with EE's depth of possibilities, we had to figure out a few tricks along the way in order to get what we wanted out of it. In this post, I'll talk about creating multiple blogs with common structures through variables, losing the nefarious /comments URL, and setting up a preview option so your bloggers can see how their posts look before publishing them.
Recent Comments
Not a bad attempt, however now you will need a tutorial called “getting rid of the blurries”.
Still leaves us with a noticeable edge blur. I wonder if there is any…
- Phil Thornton on 'Getting Rid of Jaggies on Your Photo Borders'.
- Doug Avery on 'Building Viget.com In EE (Part 1)'.
- Freelance Writing Guide on 'Why Must The Shoemaker's Children Go Without Shoes?'.
Subscribe to Comments RSS