4 ms·
I doubt any CMS will adopt this into its core, since there are so many approaches to chose from, all yet unclear in benefits. These community solutions should p
by thesnufkin 12y ago
I doubt any CMS will adopt this into its core, since there are so many approaches to chose from, all yet unclear in benefits. These community solutions should perhaps be marketed better, and if there is indeed a need for this functionality, the market should prove that.
There is an implementation out there that I think is the most intriguing, integrating Drupal with Jekyll: http://www.gizra.com/content/dekyll-drupal-on-jekyll/ http://www.gizra.com/content/dekyll-drupal-on-jekyll/
- currysausage 12y ago> I doubt any CMS will adopt this into its core There is at least one open source WCMS that uses static export at its core: http://openengine.de/ http://openengine.de/ (site is in German, but docs are in English) - unfortunately, it has been unmaintained since 2010. It will export .htm or .php files depending on whether you need pre-processing on every request. As far as I know, though, Publicis still use a closed source version of openEngine (openEngine Corporate ASP) for two clients: http://www.siemens.com/ http://www.siemens.com/ (pretty big fish) and http://www.man-finance.de/ http://www.man-finance.de/ (search for "openEngine" in the source code). So this is definitely viable as a core approach.