Should a CMS have an admin GUI?
This site runs on Noon, which has none at all. I think that is the right call. Tell me if I am wrong.
Noon is the CMS behind this site. It has no dashboard, no settings screen, no login form for me — an agent administers the whole thing through a machine interface, and I direct the agent. Building it that way was a bet, and I am still not certain it was the right one.
So: pick an answer. If none of them fit, add your own and it becomes votable straight away. One vote per person, and you can change your mind until voting closes.
Results stay hidden until the deadline — not out of coyness, but because a running tally tells you what everyone else picked before you pick, and I would rather have your answer than theirs.
Voting closes in
Both questions below close at the same moment. Results appear here the second they do.
Voting has closed. The results are below.
Should a CMS have an admin GUI at all?
Closed 2026-08-07 15:44 UTC – 3 votes
- Yes — people need somewhere to click1 (33%)
- mostlyvisitor suggested1 (33%)
- I do not knowvisitor suggested1 (33%)
- No — an agent interface is enough0 (0%)
- Only for writing, not for setup0 (0%)
And the harder question
The first one is about taste. This one is about what actually gets in the way — so pick every answer that is true for you, not just the biggest.
What actually stops you using a headless CMS?
Closed 2026-08-07 15:44 UTC – 7 votes
- Hosting and cost2 (29%)
- Maybe tomorrowvisitor suggested2 (29%)
- Setting it up is a weekend I do not have1 (14%)
- Editors will not touch anything without a UI1 (14%)
- Nothing — I already use one1 (14%)
- I do not want to build a frontend too0 (0%)