We've been building a lot of content systems lately and found Wagtail to be pretty useful (https://wagtail.io/). We build pretty much everything on Django so it's a natural fit for us.
Understanding the models and the way they show up in the admin takes a bit but it's pretty smooth after that, and very programmable. And its built-in API uses DRF, so you can expand on it with that easily. Our frontends are all React-based and it works out very nicely.
Looking at this I kind of checked out once I saw Java, which I'm not inclined to deal with these days. To each their own of course.
Java has the fastest Virtual Machine language on the market. In addition, it is possible to use GraalVM, which makes it possible to use several languages.
The Shiohara CMS currently uses Nashorn to create Javascript templates. But it is also compatible with GraalVM and we intend to add more languages supported by GraalVM to create templates.
On all the projects, you can bounce straight to the release notes. Well organized, you can bounce straight into API docs. And a demo: https://demo.shiohara.org/welcome
Almost feels like Python projects that use Flask-style docs.
Any thing planned to integrate graphql alongside/as an alternative to REST?
Adobe borrows from the periodic table.
The use of a periodic table was a way of demonstrating how products are integrated. The idea at the time was to show that AI (Artificial Intelligence) that is equal to Aluminium in the periodic table was the integration between products.
You can try out daptin. It is a headless CMS in golang. Except for the "enums" I think it should be able to help you achieve the flow you described.
Daptin has rclone integrated in it, so it can sync with BlackBlaze. Essentially you will need to do the following:
1. Declare one table
2. Make a asset column in that
3. Bind that asset column to a cloud storage(blackblaze here)
4. Daptin will expose assests as urls, but you can choose to write another action to fetch BlackBlaze url and put it in another column
If this sounds too complicated or docs are not enough (which probably would be the case) feel free to create an issue on github and ping on slack. I would be happy to help you out with your first few projects.
If it’s like a Japanese word, pronounced “Sheeo Hara” without space. Literal meaning would be “salt flats” but this pronunciation implies a surname (like “McNamara” do)
Headless-CMS makes this platform obsolete from the get go.
The modern approach of separating responsibilities dictates that a CMS should not handle the rendering of pages, but rather provide a publishing interface and "content-as-a-Service" for whatever frontend/edge-device the site is presented on.
I'm pretty sure there are cases where people don't want to have the modern approach and run two services for it. Having a random CMS taking care of these tasks is good enough for a lot of use cases.
Understanding the models and the way they show up in the admin takes a bit but it's pretty smooth after that, and very programmable. And its built-in API uses DRF, so you can expand on it with that easily. Our frontends are all React-based and it works out very nicely.
Looking at this I kind of checked out once I saw Java, which I'm not inclined to deal with these days. To each their own of course.