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.
Go the website and look at https://shiohara.org/. Top right, there are other projects and they have icons like Period Table of Elements symbols.
Example: https://github.com/openturing, https://viglet.com/turing
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?
https://openbanking.net.br/ with empty repo here: https://github.com/openbanking-net-br/open-banking
https://viglet.com/nakamoto with empty repo here: https://github.com/opennakamoto/nakamoto
IMO it'd be better to just not include them in the header if there is no code or even a TODO list to show yet.
You are right, I will remove this project from site.
Yes we are creating a set of Rest API and GraphQL to function as Headless CMS
I'm trying to do that
Post Types are displayed dynamically in GraphQL. The forecast is that by the middle of the year it will be ready
Essentially I want to create something that can export a row in a table or a item in a JSON array.
Where I can have a set of enums and fields.
And then view every with an editor but also be able to upload an MP3, have it, uploaded to backblaze and then the URL put into the field.
I could make some quick web app that does this. But I wonder if a CMS solution would help there?
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.