I’ve been thinking about how to prepare the tweet aggregation code used for the dev tweets page. I know that I want to add multiple modules to the system, and make it easy to customize the appearance of the tweet list. This sounds a lot like the WordPress model with plugins and themes, so I’m going to adopt a similar code architecture. If I do this right, others will be able to add their own plugins and themes. I also want to make installation as drop dead simple as possible. Finally, I’m going to call the code base 140Dev. I already use this name for the company and site. Why bother coming up with a new product name, only to have to rename the site and company to match the product later? And so it begins…
Decisions about the tweet aggregation code
Previous post: Twitter developer tweet aggregation is working as a plugin
Next post: Watch the losers for the next wave