Prismic Flow
Validation mode and Editor UX, Enhanced AI assistance, Design Tools
Walt
Brief
OVERVIEW
Challenge
How might we provide a validation system that guarantees production-safe data for developers while letting editors save drafts quickly and giving designers reliable, design-safe previews?
Opportunity
Build a flexible validation framework (modes + lightweight content contracts + editor UX + runtime fallbacks) that reduces runtime errors, speeds up authoring, and preserves visual consistency, all delivered incrementally and measurably.
Tools used
OVERVIEW
Background
Teams using Prismic face a trade-off: lax validation leads to fragile frontends and runtime errors, while rigid validation slows editors and encourages placeholder content, designers also struggle to keep layouts consistent. There’s an opportunity to introduce a lightweight, incremental validation framework (modes + content contracts + editor UX + runtime fallbacks) that improves data safety, speeds up authoring, and preserves visual integrity with minimal friction.
RESEARCH
Defining Problem
To align the end goals of designers, developers, and marketers, I conducted initial research using sources such as Reddit, LinkedIn, and industry blogs. This helped me gather insights into their specific needs, goals, and pain points, providing a foundation for mapping opportunities for collaboration and solution design.
Some of the thoughts shared by developers and designers alike
Using Miro for brainstorming and organizing all potential factors.
