I am looking for a quick and easy solution to setup a simple CMS. I looked around at some candidates listed below, but found nothing suitable so far.
I want to only support a single content type for a certain type of content. For the sake of explaining it assume that I want to manage books. We are going to develop some custom add-on code for processing the book data managed by the CMS. The system is going to be deployed via docker and I would like to be able to build a final image that can be deployed into production.
The following requirements should be met:
- Runs as a docker container. I'd like to build a custom image including our extensions that is deployment-ready.
- Provides a form to create an entry for a new book and edit existing entries of books
- Lists all books and provides fulltext search through all data
- Needs to have some extension possibility to add custom code for reacting to entry modifications
- Free, preferably open-source
The following requirements would be nice, but are not strictly necessary:
- File-based storage
- LDAP support
- Versioning / Auditing of entry modifications
I already looked at the following options and found them to be lacking. I might be wrong on some of these of course.
Plone: it's like throwing a nuclear bomb on a problem as big as a hairpin. It has everything needed above, but the setup and learning curve are just in another world.
Drupal: seems to be hard to get a working docker instance for the full app. The standard image requires you to do all sorts of configuration and installation initially.
grav: lacks LDAP support and apparently editing of existing book entries is hard
pico: only hosts .md files, but no support for dynamic content creation