There are always new toys in the world of technology, and people who either make these new toys, or have decided to be on their team, are ever telling us, the creators and disseminators of information, how their pet concept is the new game-changer in town. There is usually some truth in these claims, often none, but most likely it is the sleight of hand of making a new story out of old news that has only now become possible to present, package or implement in a certain way. Renamed old-wine, obvious next steps and possible side branches of information technology get touted as a revolution, and the vast majority of the herd follow with ignorant gusto. The very same can be seen at present to be happening with the idea of Apps and The Cloud.
Much of our digital world depends on a little technique discovered out of necessity in the early days of computing. This paradigm of how digital devices communicate and co-operate, makes the entirety of the internet possible and efficient. So to understand information technology and online content delivery methods, you must understand what client-server architecture is.
WordPress is one of the biggest success stories of both the open source and CMS world. In part this is thanks to their very active development schedule that has resulted in a steady stream of improvements, bug-fixes, security updates and new features, which have kept the community of its users satisfied and growing.
Over the past few years WordPress has maintained a fairly regular release schedule of a couple of major releases per year. In 2010, they released the long awaited version 3.0 which finally integrated the multi-blog fork of WordPress into the regular version and introduced the new default theme Twenty Ten, along with many improvements to do with custom post types. Having done that, they decided to take one release cycle off to work on community building and the WordPress forums, theme repository and other ancillary bits. So needless to say, the next major release, version WordPress 3.1, was enthusiastically awaited.
Food is the new art, because it is an art most of us can truly enjoy consuming. So, it isn’t surprising that food culture and the need to eat and experience new flavours and cuisines is a very popular interest throughout the world’s urban centres. Like movies before it, it is fast becoming that common interest that a large number of people get to share and identify with. It was inevitable that as the interest grew, more people would want to talk about it. Food related sites and blogs are ever growing in popularity, and food and restaurant review blogs are a large part of that movement.
Esther Tseng gave a presentation at WordCamp L.A. 2010 titled Food Blogging in WordPress. It was a good introduction to the field, with tips and insights into how best to go about it from someone who has been food blogging for a while. The video of her presentation is below to be watched (audio quality is quite bad). My notes and links to related and resources follow, for those who prefer text, and to read my own additions.
Stories and posts arranged in a decreasing order of freshness has been a model followed by many networked information sites since the fledgling days of public computer networks. BBSs and discussion forums worked on that model and blogs inherited it. In forums, where new posts could be added every few minutes by a large membership, it became clear the administrators needed a way to keep important posts displayed on top of the list permanently, not being displaced by newer content. So they invented the sticky post.
WordPress needed plugins to produce a similar effect of marking a post as sticky until version 2.7, which had a the feature built-in. This is how it works.
Look up Content Delivery in all the standard informative places and they will talk about the delivery of media content, and about the almost equivalent and mostly overlapping field of content distribution. All quite dry and academic, really, but I think almost everyone today needs to have a deeper and more intimate understanding of the tasks, issues, tools and challenges of content delivery, because increasingly we are all part of its wide scope.
For me, Drupal is one of the granddaddies of the open source CMS world. While it might not be the oldest by any means, it is the first one I tried, and loved. Even at the time, I heard a lot of complaints about how impossibly difficult it was to get to grips with. While I never shared that sentiment, and setup a reasonably active blog-like site for myself and some friends, which served us well for a few years, this accusation of unfriendliness towards the average user has continued to plague Drupal. So, it came as no surprise that when they set out to plan and design a whole new major version of the software over 3 years ago, they made the usability their main mission.
There is a lot of noise made about the fact that content is king, but as with everything else, all content is not created equal and it comes in many flavours. Time is an important factor in the importance of information. Based on its timeliness, content can be broadly divided into that which is timely and very rooted in that particular moment of history in which it is created, such as a news item, and content which is of universal interest, free from when it is consumed. This timeless content is a wonderful thing and an essential part of your content strategy. Or in simpler terms, you simply must create some timeless content.