🎃 Headless – Not Hovedløst Figured Halloween was a good time to talk about things that have lost their heads. In Danish, hovedløst means “without coherence, idea, or structure”, which sometimes sums up how headless CMS ends up being used. I’ve written a short piece on Umbraco in a headless context, what works, what doesn’t, and how we might fill in the blanks. 👉 [kjeldsen.dev/blog/headless-not-hovedloest](https://www.kjeldsen.dev/blog/headless-not-hovedloest/)

I am not knowledgable enough about Umbraco's headless parts to say anything one way or the other on this post, but it reads to me as a bunch of feature requests, have you considered creating some discussions for them? https://github.com/umbraco/Umbraco-CMS/discussions/categories/features-and-ideas I'd recommend creating one discussion per feature for focus.

I totally agree with the fact that all content types are public by default, they shouldn't be. That way you have to keep that in mind if you create any setting type of nodes as you don't want to leak any credentials. Really expected it to be the other way around

Some could be considered feature-requests, some are what I'll call design/architecture decisions I disagree with. I'll note that my "Translation items in the delivery api" has been an open discussion by Kenn Jacobsen since 2023 https://github.com/umbraco/Umbraco-CMS/discussions/15214 I will think about adding the rest - relations in content delivery api / delivery api being open by default with no acces scoping / Authorization, I am also in dialog with the Engage team about the final point.