@deadparrot @tanepiper @zachleat @dries “tags” and “the ability to put content in a hierarchy” are some examples. The issue isn’t that they are impossible with most headless systems, but that teams are left recreating CMS features from first principles with data primitives — along with the editorial interfaces to manage them.
Sometimes that’s what a team *wants*, but often it’s an unexpected shock.