1367 Studio

Here’s a quick breakdown of the journey:

The challenge


→ We needed an intuitive experience for content editors, but with strict data validation under the hood

→ Assets (images, PDFs, etc.) had to be tied directly to content with proper structure

→ We had to build some internal tools around the CMS for content QA and deployment coordination

→ Some repetitive content tasks really needed automation, but we had to create workarounds manually

The solutions

→ We leaned heavily on custom input components and structure builder to create guided editing paths

→ Created our own lightweight asset management interface within the Studio

→ Built custom logic in the frontend to mimic workflows that are now native in the Dashboard and Insights

→ Had to write a few cron jobs and server-side scripts to simulate what Functions and Agent Actions are now solving more elegantly

What we learned


→ Sanity is incredibly extensible,even before the new release, we were able to push the platform to meet very specific needs

→ Designing a clean schema from the start is key

→ Non-technical users love the Studio when it's tailored to them