✏️ New Post: How to build live CMS previews for an @eleventy site with @sanity_io

We recently built a static hotel website and wanted to enable content editors to instantly see their CMS changes in a preview window. This required very fast on-demand builds. We considered going serverless - but ended up rolling our own solution...

Read it 👉 https://www.codista.com/de/blog/live-cms-previews-with-sanity-and-eleventy/

Just deployed the first working build of my in-progress ground-up refactor of ChromeOS.dev. I've been migrating us to @sanity_io and @astro, to improve our content creation experience and our developer experience, and I've finally been able to test the whole thing end-to-end. The results? Comparable performance footprint, better DX, easier to maintain components, improved component UX, basically everything you could hope for out of a tech lift and shift.

Expect a post when it's done.

Wrote a step-by-step guide on how to migrate a @sanity_io Studio in place from v2 to v3, including some common customizations.

Summary: Less code. Fewer dependencies. Faster development. More flexibility.

https://www.sanity.io/docs/example-migrating-the-blog-template-from-studio-v2-to-v3

This is all the code you need to run a @sanity_io Studio for a simple blog in any JS/TS project.

➤ Real-time‚ responsive, customizable content workspace
➤ Query content with GROQ/GraphQL
➤ Asset pipeline with on-demand transforms
➤ Fine-grained document revisions
+++

One thing I love with @sanity_io Studio v3 is that loads of (real-time) information is now available in async callback functions in a lot of places, including the slug field.

If this intrigues you, then you should totally join us today!

https://www.sanity.io/productday?utm_source=mastodon&utm_medium=organic_social&utm_campaign=sanity-product-day&utm_content=

That feeling when you finally get to officially release something the team has spent over a year making and even more thinking about.

So stoked for @sanity_io Studio v3 going GA next week. 🥰