- "Even FOSDEM has, as of the 2013 edition, replaced Drupal with nanoc, a popular static site generator."
- We have been working hard to revise the website in order to make it easier to modernize, accept contributions, and internationalise. The main part of this is switching the underlying technology from WordPress to Jekyll.
Idea
Tiki could become (also) a Static Site generator. This could be done like Sculpin does it.
Why do it
- Performance: static HTML and image files are faster. A CDN can be used for all content, not just CSS and JS
- Security: fewer attack vectors
How
Site visitors would be on the static HTML generated by Tiki (example.org)
Editors would go to a different URL that could be on a different server (editor.example.org). This could be higher security. Ex.: Restrict access by IP address, 2 factor auth, etc.
Then, static HTML regenerated by Tiki as the site editor decides and it replaces the current HTML. This would be a subset of available Tiki features and it could be a subset of the available content (only content visible by anonymous)
Why not do it
- It's extra work and ongoing maintenance.
- Will people really use it?
To investigate
Related links
- https://www.staticgen.com/
- http://www.mickgardner.com/2012/12/an-introduction-to-static-site.html
- https://www.openhub.net/tags?names=static_site_generator
- https://github.com/cebe/js-search
- http://www.metalsmith.io/
- http://symfony.com/projects/spress
- https://wordpress.org/plugins/static-html-output-plugin/
- https://en-ca.wordpress.org/plugins/wp-super-cache/
- "This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts."
- https://github.com/abecms/abecms
- https://anarc.at/blog/2018-10-04-archiving-web-sites/
- https://vuepress.vuejs.org/
Why?
Related
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}