"The Big Green Button" for static/SQL content mirroring
"The Big Green Button" is an idea that has been floated around to make it easier to push plone content to a static web server or to a sql database. Plone becomes just the content management tool and not the content delivery server.
http://www.martinaspeli.net/articles/pete-and-andy-try-plone-4
http://blog.kapilt.com/2008/07/02/introducing-content-mirror/
http://blog.delaguardia.com.mx/hosting-options-plone-adoption-and-the-big-green-button
Lee Joramo
shared this idea
3 comments
-
Wojciech Lichota
commented
There is also http://pypi.python.org/pypi/stxnext.staticdeployment - similar solution for enpraxis.staticsite.
-
natea
commented
I heard from Brent Lambert of EnPraxis that they have built a tool for publishing Plone content as static HTML. http://pypi.python.org/pypi/enpraxis.staticsite/
-
Ken Wasetis
commented
I believe that ContentMirror and Entransit are limited to 'pushing' content out of the Plone CMS into relational database tables or to XML, but that static HTML files are not currently an option. For that, we can use CMFDeployment or possibly a Linux tool such as wget.
Here is an effort and team already organized toward this feature (static publishing.) Since starting this project at openplans.org, now coactivate.org, I have dropped the ball due to focus on some other projects that I hope to release to the collective soon.
If you'd like to get the ball rolling more with this static publishing feature, that would be great. I don't believe that ContentMirror or Entransit do the same type of link crawling that CMFDeployment does, so I think CMFDeployment is the best start toward a good 'green button' static export of a Plone site that can be uploaded to a $5/month hosting server (unless a webmaster can get just the right wget options in place to use that without broken links.)
See/join the coactivate project on static publishing from Plone here:
http://www.coactivate.org/projects/plone-static-publishing/project-home
