During the past few weeks I have been working more or less silently on a proof of concept for a natively Neos-powered blog. This is an important milestone, as it is supposed to prove the concept of our node-based content repository and the powerful rendering mechanism of TypoScript 2 and Fluid.
Today I finally deployed the new blog and migrated all posts from the previous standalone Flow application. The goal of this exercise is not just a plain blog example, but, in the end, a full-featured blog application with a great user experience. I think that the combination of Neos' content editing concepts and the power of the Flow framework underneath will let quite a few people consider again if their current blog solution is easy and powerful enough for running their website.
But back to present. The nicest feature of my blog prototype is the seamless integration into Neos. Blog posts are just page-like nodes which are rendered by Neos like any other content. Even comments of a blog posts are just "regular" content which can be reviewed and edited in the Neos user interface. I can edit blog posts in my personal workspace and preview them right on my version of the website before publishing them.
Finally I can insert images anywhere I like and provide code examples inline!
As I wrote, this is currently a solution working for my site and meant as a proof-of-concept. Much more thinking and development needs to go into a full-featured blog plugin. However, once the work is done, the solution can be easily used as a news system, magazine solution or solve other tasks which need to deal with article-like content.
As of today it's not clear yet to which degree the TYPO3 Association will fund the development of Neos and Flow (but we're expecting a statement by the Expert Advisory Board soonish). So by now I've been working off my piggy bank to create this prototype and implement the missing features in Neos.
I know that many of you can't wait to start your website with a powerful news or blog system based on Neos. If you're one of them, please consider sponsoring your pet feature and some clean up of the current code base. If I find the time, I'll gladly write some more posts about the technical details of my blog.
So, what are your thoughts on a Neos powered blog? Which approach or feature would you like to see implemented?