Skip to content

Rationale

Robert Speck edited this page Mar 8, 2016 · 4 revisions

Why Static Page Generator and not Wordpress?

All dynamic content management systems (CMS) such as Wordpress, Joomla, Drupal, Typo3, etc. have one thing in common: They are server side applications running at all times proxied through the actual web/http server.

This induces one important and huge obligation: Keeping the CMS software up to date patching repeatedly occurring security bugs.

Websites produced by a static page generator, such as Jekyll, are served directly by the web server. Thus, there is no additional server side software running, which needs to be kept up to date. Jekyll is actively developed and has a large community with loads of guides and help.

In addition, editing content on a CMS based website requires setup and management of user accounts. In most cases there is no intrinsic way of reviewing modifications of account holders before them going public.

With sticking to GitHub's pull requests, everybody (worldwide) can add content, however, only those pull requests accepted by the maintainers of the website repository will make its way onto the public website.