Add Decap CMS to static websites #554
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#554
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decap CMS is a nifty headless CMS which supports popular static site frameworks (Hugo, Gatsby, etc.) it allows editing of frontmatter (YAML) in a user friendly interface. Decap connects to a git-forge backend like GitLab or Gitea to access the data from the static sites repo.
I think it would useful to lower the barrier of entry for people who are not programmers / comfortable with CLI to edit Co-op Cloud websites and documentation. Also it is nice to see a preview of your content in a GUI web page view before committing without installing local dev environment.
Sites where this could be created and used for Co-op Cloud are:
I will generate a Decap config for the main website so you can see the experience.
It's a great idea IMHO. Not familiar with Decap but curious to see it in action. If we could unify the sites under a single Hugo install with a GUI for editing content, I think that would be a pretty smooth workflow. Might be a considerable amount of work tho?
Cool. I am glad the idea is well received 😄 If the sites were already all Hugo, it would definitely be easier. I'm not sure if mkdocs can be edited via Decap, that would be a bit of Research (and maybe Dev) effort, but it might be worth it as that is a pretty nice theme for documentation heavy sites and it looks pretty similar to Hugo.
So according to
mkdocs
anddecap-cms
it should work, so I pushed a WIP bit of that to decap-cms branch.awesome idea, excited to see how this works out. let me know if you want help getting an instance going on the co-op cloud servers.
this is a custom app (in Elm for some reason) and most of the content (descriptions and metadata) are all pulled from recipe repos. but if there's a way to make the minimal hardcoded content editable through Decap that'd be gr8
Sweet 😄 I think the main thing (which is probably) needed is getting the Gitea CORS settings configured correctly. This is what Codeberg did to enable CORS on their infrastructure.
Yah, after poking around at the Elm codebase, I don't think integrating Decap on top of it makes sense as it wold be a lot of work I think.