This post originated from an RSS feed registered with Python Buzz
by Carlos de la Guardia.
Original Post: Blogging my Plone Conference presentation
Feed Title: I blog therefore I am
Feed URL: http://blog.delaguardia.com.mx/feed.atom
Feed Description: A space to put my thoughts into writing.
Well, I finally uploaded my presentation for this year's Plone Conference to slideshare last week. However, since it is just a bunch of images with barely any words, I don't imagine it will be very useful to anybody. That's why I decided to do this experiment and blog my presentation, one slide per post, over the next few weeks.
My talk was entitled "The big green button - turning Plone into a dynamic site factory". This is in reference to a thought provoking article about the future of Plone by Martin Aspeli (see day 10, right at the bottom of the post), where he dreams about a scenario where deploying a Plone site as a PHP application or as a simple static site is done by pushing a big green button in Plone's control panel.
This subject has been very important to me for some time now and I think that's a feature that would be very, very useful in the Plone World. Which is why, when I was given the chance to lead a project like this by the National Library of Congress in Chile, I jumped at it.
The project's main objective is to have a single Plone site for managing the content of several public sites, which is an scenario many media sites and public organizations may face. The strategy we selected is to use Plone only as a CMS, which is what it does best, and decouple the delivery of the content, allowing a dynamic Python web application to perform this last task.
What I will be blogging about in the following days, is the thought process, tool selection and project progress and benefits which came as a result of pursuing this strategy.
Previous Topic
