Storing Templates and Object-Oriented vs Relational Databases
I'm a huge Oracle booster but I think you should seriously consider NoSQL. Cassandra and other NoSQL Databases have already considered your conundrum and have smashed it down to the ground. CouchDB is another who, I believe their example code is how to store a blog.
I'm designing some custom blog software, and have run into a conundrum regarding database design.  The software requires that there be multiple content types, each of which will require different entry forms and presentation templates.
My initial instinct is to create these content types as objects, then serialize them and store them in the database as JSON or YAML, with the entry forms and templates as simple strings attached to the "contentTypes" table.  This seems cumbersome, however.  Are there established best practices for dealing with this design?  Is this a use case where I should consider an object database?
If I should be using an object database, which should I consider?  I am currently working in Python and would prefer a capable Python library, but can move to Java if need be.