Add Decap CMS to static websites #554

Open
opened 2024-01-26 11:13:50 +00:00 by basebuilder · 5 comments
Member

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:

  • coopcloud.tech
  • docs.coopcloud.tech
  • recipes.coopcloud.tech

I will generate a Decap config for the main website so you can see the experience.

[Decap CMS](https://decapcms.org) 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: - [ ] coopcloud.tech - [ ] docs.coopcloud.tech - [ ] recipes.coopcloud.tech I will generate a Decap config for the main website so you can see the experience.
basebuilder added the
enhancement
label 2024-01-26 11:13:50 +00:00
Owner

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?

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?
Author
Member

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.

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](https://squidfunk.github.io/mkdocs-material/) 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.
Author
Member

So according to mkdocs and decap-cms it should work, so I pushed a WIP bit of that to decap-cms branch.

So according to `mkdocs` and `decap-cms` it should work, so I pushed a WIP bit of that to [decap-cms](/coop-cloud/docs.coopcloud.tech/commits/branch/decap-cms) branch.
basebuilder added this to the Improvements to Websites milestone 2024-02-06 11:06:16 +00:00
Owner

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.

recipes.coopcloud.tech

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

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. > `recipes.coopcloud.tech` this is [a custom app (in Elm for some reason)](https://git.coopcloud.tech/coop-cloud/recipes.coopcloud.tech/) 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
Author
Member

...let me know if you want help getting an instance going on the co-op cloud servers.

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.

> ...let me know if you want help getting an instance going on the co-op cloud servers. Sweet 😄 I think the main thing (which is probably) needed is getting the Gitea [CORS settings](https://docs.gitea.com/administration/config-cheat-sheet?_highlight=cors#cors-cors) configured correctly. This is what Codeberg did to [enable CORS](https://codeberg.org/Codeberg-Infrastructure/build-deploy-forgejo/commit/087cc47069f58709b6000b1934d3cefd2da4a753) 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.
Sign in to join this conversation.
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#554
No description provided.