More and more developers are jumping on the "go static train", and rightfully so. Static pages are fast, lightweight, they scale well. They are more secure, and simple to maintain and they allow you to focus all your time and effort on the user interface. Often times, this dedication really shows.
It just so happens that static site generators are mostly loved by developers, but not by the average content editor. They do not offer WYSIWYG, previewing on demo sites may take an update cycle, they are often based on markdown text files, and they require some knowledge of modern day repositories.
Moreover, when teams are collaborating, it can get complicated quickly. Has this article already been proof-read or reviewed? Is this input valid? Are user permissions available, e.g. for administering adding and removing team members? Can this article be published at a future date? How can a large repository of content be categorized, organized, and searched?
An alternative is decoupling the content management aspect from the system. And then replacing the maintenance prone server with a cloud based web service offering. Effectively, instead of your CMS of old, you move to a Content Management as a Service (CMaaS) world, with a content API to deliver all your content. That way, you get the all the benefits of content management features while still being able to embrace the static site generator mantra.
A service that
In order to be completely removed from everyday site management and maintenance, we suggest following the approach from Carrot Creative. In addition to an API driven CMS system, you will need a hoster that supports webhooks and is capable of starting builds and deploying websites.
Sign up to a WebriQ account now! There is free testing plan which will most likely suffice for most small projects. For bigger projects, you can upgrade to our PRO plan.