Having read through all of the material in the blog post and several related requests, as a 20+ year digital veteran and enterprise UX manager, my point of view is pretty simple.
I think the Prismic team is over-stepping their implied authority by enforcing their vision of an open-ended free for all of content entry by dictating terms to UX teams who know their product and it's requirements far better than they do.
This is a crazy hill to die on if you're going to pick a lost cause, and it's one of the major reasons that it's hard to get a big company to take Prismic seriously despite everything it does vastly better than the other headless CMS systems.
For ***k's sake folks, let the teams using Prismic decide whether or not they need input validation on a phone number or a hard limit of 3-up on core concept pillars. It really isn't your job to save them from your own opinion about the slippery slope of bad design.
Meanwhile setting up NextJS validation hooks to warn me every time a client does something that might break the layout of a site is a GIGANTIC pain in the a**.
Thank you for taking the time to provide us with your feedback.
Regarding your concerns about required fields and input validation, I want to let you know that we recognise the need to review these features (more precisely the fact that we don't yet support them) based on feedback like yours. We understand the need for teams to have control over their content models and workflows, and we're considering ways to offer more flexibility.
At the same time, part of our mission is to ensure that the user experience remains consistent and intuitive. As Renaud expressed in his blog we are opinionated on this topic and that remains the case today. We want to ensure we provide a good user experience, so any solution we design will keep the considerations outlined by Renaud in mind.
Thanks again for your input, and I'll post an update on this thread once we begin to look into this topic in more detail (most likely in H1 2025).
I've spent a lot of time twisting my brain around things like complex content relationships in MegaMenus and extending Descope/Supabase to allow for integration with Hypothesis and access control. A lot of little hooks could be cleaner for that kind of dev and the abstraction gets a bit wild. Being unable to control some of the details on the user end can be a bit infuriating after hours of wrestling with other elements.
But the way you lay out slices and allow them to hook into the rest of the React/Next ecosystem is really hard to beat, especially at the price to value point we're talking about.
When I vent my frustrations it's only because I still prefer Prismic's approach to trying to make Sanity or Builder or something try to do the same thing. I mostly just have a wishlist that would make my life easier
No worries - I understand where you're coming from. For what it's worth we currently have a feature that explores a pattern around field validation, in the context of SEO metadata. Essentially if the field is empty we show a modal where we have generated copy of for the field and the user can approve and publish or update the field within the modal. There is also some light validation for the field i.e. it shows the recommended number of characters for an SEO metatitle or metadescription. You can read more about the feature here and I'll update this thread in the future if I have more updates on this topic.
