Update: This contest has been extended to March 30, 2007.
There is an often-overlooked aspect of WordPress that adds functionality that is more geared to a Content Management System than a blogging platform. And that’s why, perhaps, the world’s #1 blogging software finds that many users don’t really use Custom Fields.
I think that’s a travesty.
Conversations in the blog software world always toy with concepts that look forward to what should be introduced in a blogging software. A lot of these conversations circulate around breaking blogs out of the status quo which are “typical blogging templates”. Different approaches were taken at different times in the history of the blogging platform. For instance, the conversation around categories and how conversations could really be more granular than simple categories led to the advent of tags which are seen around the blogosphere. Trackbacks were used to alert another party of your conversation surrounding them but as spammers started exploiting trackbacks, pingbacks were invented which were more passive and allowed discovery of conversation surrounding the blogger.
Evolutions come and go, yet, blogging by and large remains a linear concept that is driven mainly by content creation and reader interaction. To that end, themes are built to this standard.
But what if the standard is just too limiting? What if the standard can be enhanced and changed? What if simple personal blogs could be turned into effective content properties?
Custom Fields may be the answer to the question, how do you make the mundane reach these goals?
I’m running a contest here at Technosailor and there are prizes involved. There is also judging. But there is time.
It probably interests no one but me, but I’m becoming more of an SVN ninja. It took me days to figure out how to setup a web accessible SVN server with appropriate web, svn and filesystem permissions (i.e. this repository is world readable, but can only be written to by me). I’ve been using SVN on the client side for a couple of years now, though not as a ninja, because of WordPress. In essence, I was downloading nightly builds of WordPress when it was 1.6-alpha (what would become the 2.0.x branch). Now, I am building everything on top of SVN, from plugins to personal projects, to contractor projects and on. Repositories are a commodity and with change control and versioning, it makes it dirt easy to revert when something is broke.
So I took the next logical step personally, and wrote a cron job to automatically svn me to trunk every day. That means I’ll always be running the latest.
Q: What if WordPress introduces a bug that breaks the blog?
A: I can easily revert back to an early revision thanks to SVN.
Q: Why run unstable software?
A: Because this is a biggish blog (Top 2600 in Technorati today, whoo!) and no better way to find bugs and squash them before WordPress 2.2 is launched (in Aprilish) than to run trunk constantly in a big environment. WordPress.com runs trunk as well, so if it’s good enough for them, it’s good enough for me.
Q: Aren’t you worried about hackers?
A: I’ll answer this gently… Not really. I don’t invite them to hack me, but if they do then it’s good exposure on a flaw and we have kick-ass backup support at LogicWorks. So no, not really. The good outweighs the bad here.
A few of you have been asking me about when Timecapsule (initially released on Problogger) would be WordPress 2.1 compliant. The time is now and not yet.
For those who wish to download and test (please do!), you can do so via SVN:
svn co http://svn.b5media.com/svn/timecapsule/trunk
Or download the nightly.
I am looking to take this plugin to the next level and build features so speak up if you want features. Hart, this means you. And anyone else. :-)