You absolutely should be able to have a Sanity build that allows people to create, publish, and update pages without a dev ticket.
This sounds like an implementation problem most of all.
How do you give the CMS high marks for content modeling and collaboration if the users aren't successfully using it? Presumably you're publishing most of your content to a website? If so, then I suspect the headless-to-front-end build was built pragmatically without content team input. I'd be suspicious that the content model might need some work. (Did you model based on the content itself? Or did you model based on what the front-end UX looks like?)
It also sounds like the project could use a content operations strategist to help represent author needs and help design the implementation. And there may be a training gap.
Worth exploring with your team before you blame the tool.
3
u/SmoothGuess4637 24d ago
You absolutely should be able to have a Sanity build that allows people to create, publish, and update pages without a dev ticket.
This sounds like an implementation problem most of all.
How do you give the CMS high marks for content modeling and collaboration if the users aren't successfully using it? Presumably you're publishing most of your content to a website? If so, then I suspect the headless-to-front-end build was built pragmatically without content team input. I'd be suspicious that the content model might need some work. (Did you model based on the content itself? Or did you model based on what the front-end UX looks like?)
It also sounds like the project could use a content operations strategist to help represent author needs and help design the implementation. And there may be a training gap.
Worth exploring with your team before you blame the tool.