In our previous installment we looked at setting our backend up so it could automatically retrieve the bit.ly URL for a given URL and store it as part of the data for a given instance of a Content model. What we're going to do this time is take a look at the front end components.

Sometimes I find that doing things backwards can actually make things a little more clear. That way you can see the end result and then, as you work backwards, see how all the pieces work together.

Well another week, another set of changes. There are 4 primary changes that I've made to the site since last week. They are, in no particular order

Email subscriptions The addition of comments. A Twitter-based rating widget Related links

Related Links

Over here there is a good article on sharing page feedback on Twitter. I'll end up doing something similar but in a different manner. A little while I posted an article (Do you queue?) on how you could use the Zend Server Job Queue to run individual tasks. Well you can do the same thing here. I've made a few changes since that article, namely that Zend_Application is passed in both to execute() and to run() so I could easily retrieve application settings. Don't know why I didn't think of that earlier. Oh well.