Thread by @ddprrt

The tsconf.eu website runs on the JAMstack, and by now I'm 100% convinced that #JAMstack is not only a technically advanced architecture but also advanced in terms of editor experience. Here's our setup:

For the prod site, everything is as you would expect it. We use an SSG (@nuxt_js), fetch content via API from @storyblok and publish it on @netlify. Netlify deploys on merge to master, but also when Storyblok calls a hook. That's how we get up to date content.

The clue is: We run @nuxt_js in app-mode on @zeithq's now as well. This version does not generate sites but fetches the draft version directly from @storyblok

This version gives us in-page editing that's on par, if not better than popular CMSs

And you get all the Benefits of a JAMstack setup: Within an hour, we removed our CMS driven ticket section and fetch data directly from our ticket provider @useTito. Tito also calls @Netlify via hooks if something has changed

This allows to manage ticket section content just once, plus we can run the same again in prod mode (fetch the data you need), via live mode (show real-time data while editing).

An integrated editing solution, no matter where the content comes from. In almost no time. Wow. 👏