#decapcms — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #decapcms, aggregated by home.social.
-
We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]
The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:
1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).
2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]
3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.
4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.
Documentation is also about building inclusive pipelines!
Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon
@ioer @diegorybski.bsky.social
[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/ -
We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]
The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:
1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).
2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]
3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.
4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.
Documentation is also about building inclusive pipelines!
Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon
@ioer @diegorybski.bsky.social
[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/ -
We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]
The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:
1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).
2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]
3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.
4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.
Documentation is also about building inclusive pipelines!
Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon
@ioer @diegorybski.bsky.social
[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/ -
We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]
The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:
1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).
2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]
3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.
4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.
Documentation is also about building inclusive pipelines!
Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon
@ioer @diegorybski.bsky.social
[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/ -
We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]
The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:
1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).
2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]
3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.
4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.
Documentation is also about building inclusive pipelines!
Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon
@ioer @diegorybski.bsky.social
[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/ -
I want to share my experiences with #DecapCMS [1]. I set up a lot of static pages with #CI&CD in the past. #mkdocs material, #jekyll, #hugo. You name it. The challenge was always to bring in people not comfortable with #Git/ #Gitlab.
DecapCMS elegantly solves this without much overhead: You place a `js`, `config.yml` and `index.html` in your static site. DecapCMS connects to your Gitlab (or #Github etc.) via Application integration. Tada. Your users can now edit your Markdown based static site directly in a #WYSIWYG-like editor, without ever touching Git, Gitlab or Github. The backend and CI&CD all remain the same.
I had this on the radar for a long time, but only now was able to test it. The integration and setup process was much simpler than I thought. No additional service required, just static files!
-
Kennt sich jemand mit #decapCMS aus? Ich versuche eine Konfiguration oben in jede Seite reinzubekommen und schaffe es nicht. Falls da wer einen Tipp hat wäre ich dankbar.
Das soll oben in jeden header, bonuspunktem wenn man noch nen schalter hat für true/false :)
```
[build]
publishResources = false
```
Danke! -
Kennt sich jemand mit #decapCMS aus? Ich versuche eine Konfiguration oben in jede Seite reinzubekommen und schaffe es nicht. Falls da wer einen Tipp hat wäre ich dankbar.
Das soll oben in jeden header, bonuspunktem wenn man noch nen schalter hat für true/false :)
```
[build]
publishResources = false
```
Danke! -
Kennt sich jemand mit #decapCMS aus? Ich versuche eine Konfiguration oben in jede Seite reinzubekommen und schaffe es nicht. Falls da wer einen Tipp hat wäre ich dankbar.
Das soll oben in jeden header, bonuspunktem wenn man noch nen schalter hat für true/false :)
```
[build]
publishResources = false
```
Danke! -
Kennt sich jemand mit #decapCMS aus? Ich versuche eine Konfiguration oben in jede Seite reinzubekommen und schaffe es nicht. Falls da wer einen Tipp hat wäre ich dankbar.
Das soll oben in jeden header, bonuspunktem wenn man noch nen schalter hat für true/false :)
```
[build]
publishResources = false
```
Danke! -
Moltíssims llocs web fets amb CMS poden refer-se amb generadors de web estàtiques i millorarien en rapidesa i seguretat. A més, el manteniment passa a ser molt menor.
Amb la combinació de #Hugo i #decapCMS es pot aconseguir tenir una solució ràpida, òptima, segura i fàcilment editable.
Si vols que t'ajudem a fer aquesta conversió, parla amb nosaltres!
-
I like what #tinacms has to offer in terms of a git-based #CMS, but I loathe #React and #NextJS . They support #hugo as far as I can tell, but their starter template doesn't work. Crashes during startup 😒
#decapcms seems like a reasonable alternative. Plenty of support for many #ssg tools like #11ty, but the editing experience in #decapcms is pretty boring. Doesn't really offer anything for me beyond what I could simply do with text files.
I want a decent editing experience, where I can both author blog posts, but also build my web-site using blocks/components. #Tinacms seems pretty ok all around, but looking at the starter sample, the code is crazy convoluted. There is more wrapper-code and boilerplate than there is actual HTML. Hard to know where to even start.
#cloudcannon has an excellent alternative. If this was free for individuals, I'd jump right on that. But I'm just running a little personal website that makes no revenue, so I don't want to fork out $50 a month for it.
Anyway, #sendhelp
-
Looking for CMS advice
Hey Web devs!
Do you have any suggestions, tips, opinions, dos, don’ts about headless CMSes?
I have a growing list of small/mid non-profits and collectives asking for my help to (re)make their website. I totally want to help, but I don’t have much time, especially considering that they generally have little or no funding—I would most definitely point them to @VillageOneCoop, otherwise.
Therefore, I want a super simple and replicable solution where I can copy-paste most of the code, while providing them with a stable, fast, and modern solution. I had a look at the Headless CMS section in the Jamstack website, but I need opinions from people who actually used some of that software already.
Needs
- I want to code and configure everything using @eleventy
- Admin interface (#WebApp) for the client to add pages and write posts
- Static website in the front-end
- Simple and reliable CI/CD
- No/minimal maintenance after the first setup
- Self-hostable (I was taking this for granted so much that I forgot to write it)
- If it requires forge integration, it should support #ForgeJo
- #OpenSource
Nice to have
- Possibly using #Deno, not #NodeJS
- Allowing the client to customize a bit their website through the admin interface, with a GUI
- CMS app packaged on @yunohost
- No CMS vendor lock-in
- I’d love to write as little JavaScript as possible
- #FreeSoftware
Absolutely not
- Front-end #JavaScript frameworks
Please, boost this and ask around! Links to videos, tutorials, and resources are welcome.
People whose perspective I would really value: @zachleat @harryfk @deno_land @jaredwhite @vanillaweb @stefan @mxbck @WeirdWriter @deadsuperhero (Sorry if I am spamming you!)
#Eleventy #11ty #CMS #HeadlessCMS #Ghost #DecapCMS #CraftCMS #Strapi #Web #WebDev #WebDesign #StaticGen #StaticWebsite #Website #HTML #CSS #YunoHost #SelfHosting #Wordpress
-
I finally got around to doing something with my blog again. I added #decapcms to my #jekyll based site.
Now I just need to write the next post on the integration with @ubernauten
Short Post:
https://jkoan.de/posts/decap-cms-das-admin-interface-f%C3%BCr-statisches-html.html
#blogging #blog -
. the integration is effectively zero effort. i didn't want to add extra npm build / run steps for my end users, otherwise #tinacms was also a frontend i had considered.
. fully local file editing is HUGE for me, probably the biggest reason i didn't use DecapCMS instead. i don't like adding the netlify OAuth dependency and all that entails, and i just wanted a workflow for my users to edit files locally and pass them into a pull request later. it's a bit weird that it's only supported in Chrome/ium, and i hope the file editing API has support for firefox-based browsers in the future.
. lack of custom components hurts a lot. i wanted the ability to have tweet and PDF.js embeds, but there isn't direct support for custom components yet. I ended up making a workaround by using partials that pick up the data from post attributes and embed them directly at the bottom (which is feasible for my specific requirements but probably generally a bad idea)
. no support for Hugo's page bundles is frustrating. i like to organise my assets alongside my posts, although maybe that's more sensible in a VSCode / obsidian workflow than a CMS workflow. had to reorganise my asset files to make it work, and i worry it won't scale well to ~1000 posts (which i don't need anyway). there is category-level asset organisation, but even that is really insufficient
. field customisation is a 10/10 from me. the configs expose all the options that i would've liked, it looks pretty, and there's even support for adding individual pages. custom slugs are great to have too. i would like to see some enum style arrangement for category fields if possible to avoid typos.
. i'm still unfamiliar with the nuances of Hugo, and the template language is quite intimidating to learn (no prior experience with JS components doesn't help). regardless, it was simple enough to hack together some patches onto the theme
. i might want some sort of folder organisation on my admin page in the future, though i don't know if that's already doable with some configuration 😅. the project is not at that scale yet though.
-
. the integration is effectively zero effort. i didn't want to add extra npm build / run steps for my end users, otherwise #tinacms was also a frontend i had considered.
. fully local file editing is HUGE for me, probably the biggest reason i didn't use DecapCMS instead. i don't like adding the netlify OAuth dependency and all that entails, and i just wanted a workflow for my users to edit files locally and pass them into a pull request later. it's a bit weird that it's only supported in Chrome/ium, and i hope the file editing API has support for firefox-based browsers in the future.
. lack of custom components hurts a lot. i wanted the ability to have tweet and PDF.js embeds, but there isn't direct support for custom components yet. I ended up making a workaround by using partials that pick up the data from post attributes and embed them directly at the bottom (which is feasible for my specific requirements but probably generally a bad idea)
. no support for Hugo's page bundles is frustrating. i like to organise my assets alongside my posts, although maybe that's more sensible in a VSCode / obsidian workflow than a CMS workflow. had to reorganise my asset files to make it work, and i worry it won't scale well to ~1000 posts (which i don't need anyway). there is category-level asset organisation, but even that is really insufficient
. field customisation is a 10/10 from me. the configs expose all the options that i would've liked, it looks pretty, and there's even support for adding individual pages. custom slugs are great to have too. i would like to see some enum style arrangement for category fields if possible to avoid typos.
. i'm still unfamiliar with the nuances of Hugo, and the template language is quite intimidating to learn (no prior experience with JS components doesn't help). regardless, it was simple enough to hack together some patches onto the theme
. i might want some sort of folder organisation on my admin page in the future, though i don't know if that's already doable with some configuration 😅. the project is not at that scale yet though.
-
integrated sveltia-cms into my existing hugo project today. some notes ✍️
note: the project is currently in early integration so many things might end up different later on, or my assumptions might be incorrect.
-
integrated sveltia-cms into my existing hugo project today. some notes ✍️
note: the project is currently in early integration so many things might end up different later on, or my assumptions might be incorrect.
-
Eeeh, took a few moths break from a #web-dev project that used #StaticCMS as a #Git-based #CMS for a #StaticSite and now I'm learning it is archived and development has stopped 😅
Any toughts on alternatives? #TinaCMS? #DecapCMS? Is Netlify funding the latter? Is Netlify evil?
-
#HELP! I've been working with a team of geographers to build a #Palestine curriculum at the intersection of space and politics.
We want to publish a bilingual website with the content.
I tried to polish my rusty techie mind, and built a something using #Hugo. But got stuck making the #DecapCMS to recognize the translated content.
Do I know any nerds here who can help me fix this?
Also here's a pic I took when I was in Palestine in 2023 (near depopulated village Hittin).
-
New #blost for #100DaysToOffload
Post 65/100.
My review of DecapCMS.https://orbitalmartian.gitlab.io/posts/a-great-cms-decapcms-review/
#DecapCMS #CMS -
is there a thing called developer adhd ?
I do know that i might be in the range BUT here me out :
everytime im diving into a project then as i work on it i get cought up in uuuuh but what about this intergration or that or that
for the last couple of years if have been building steady my #11ty website build with a cms in the backend using #decapcmsbut now after a week of looking suddenly its uh but what about #tinacms / frontmatter...
its like no focus at all or am i just to curious ?
-
-
I didn't realize quite how big this site was. It's got about 560 content items across five content types, but I'm able to scrape just about everything. I'm throwing in #decapcms to manage it, and it's working perfectly so far.
This may be the most complex Eleventy site I've built so far. My personal site has a comparable amount of content, but in this one, the content is full of references to other content items.
-
working with #eleventy and #decapcms (former #netlifycms ) is pretty awesome
With one exception the use of the word collections
one is a collection of data the other is a contentype / pagetype kinda thingieNaming stuff is hard
-
CW: Static site generator shop talk, self-hosting, decentralised web
While working with a student, I am being caught up to this entire #Netlify #NetlifyCMS #DecapCMS #StaticCMS cascade and I am so exited.
I have not worked on many web dev projects in the last few years, but the CMS question has always been a painful one for me. I chose Bludit for the last project I worked on but was never all that happy with it.
The idea of a #selfhosted #CMS with a UI that effectively creates commits to Git a git repo is really fun to me.
The inherent super heavy JS reliance remains a question mark, but it does seem like a step forwards for decentralised web conversations and self-hosting projects.
-
So, #NetlifyCMS got a new name a couple of weeks ago: #DecapCMS. But right before Netlify announced the new owner/name, a community fork called #StaticCMS was created. And – compared to Decap CMS which is still mostly dormant – the fork actually put a lot of work in and is about to release a new major version v2 in about two weeks. I'm really excited for this new version to be a proper successor to #NetlifyCMS. https://github.com/StaticJsCMS/static-cms #CMS #WebDev #Jamstack #StaticSiteGenerator
