Help me choose a CMS
Posted: Fri Jul 15, 2016 10:00 pm
SO. Work project. Need a CMS.
Requirements:
Needs to be able to output a static site. HTML, CSS, JS, nothing else. (This could be done in a pinch with wget, but that tends to break forms.) The idea is that the CMS itself will run on a development server on the LAN, and then deploy to a production server; we don't want any exposed server-side scripts or databases on the production server.
Needs to have a simple WYSIWYG editor for end users. (This rules out command-line kits like Jekyll.)
End users need to be able to preview their updates before deploying. (This rules out using a headless CMS. Because if I were, say, to use Drupal for the CMS on the dev server and have it send JSON data to a JS frontend on the production server, that means I would have to write two different versions of the same theme, one for Drupal and one for the frontend toolkit, in order for end users to see the same layout on both servers.)
Free (as in speech and beer).
Nice to have:
I'm going to build a theme for the thing, and I'm going to use Bootstrap. Something that's got already-available Bootstrap themes is a plus but not a requirement.
An easy-to-use, well-supported plugin architecture would be a good idea.
So far the only thing we've found that matches the requirements is OpenCMS. I do not like OpenCMS.
Requirements:
Needs to be able to output a static site. HTML, CSS, JS, nothing else. (This could be done in a pinch with wget, but that tends to break forms.) The idea is that the CMS itself will run on a development server on the LAN, and then deploy to a production server; we don't want any exposed server-side scripts or databases on the production server.
Needs to have a simple WYSIWYG editor for end users. (This rules out command-line kits like Jekyll.)
End users need to be able to preview their updates before deploying. (This rules out using a headless CMS. Because if I were, say, to use Drupal for the CMS on the dev server and have it send JSON data to a JS frontend on the production server, that means I would have to write two different versions of the same theme, one for Drupal and one for the frontend toolkit, in order for end users to see the same layout on both servers.)
Free (as in speech and beer).
Nice to have:
I'm going to build a theme for the thing, and I'm going to use Bootstrap. Something that's got already-available Bootstrap themes is a plus but not a requirement.
An easy-to-use, well-supported plugin architecture would be a good idea.
So far the only thing we've found that matches the requirements is OpenCMS. I do not like OpenCMS.