You’ve built your Next.js site and now you want to put it online for the world to see. Which platform is the best to host it?

This quick-hit breakout session discusses all things image-related in live Q&A. We touched on pre-loading images and image optimization best practices on Gatsby sites.

Jamstack and personalization: people say it’s possible, but no one’s shown you a real-world project with implemented personalization. Until now.

Let's add some automation into a headless CMS workflow process by using webhooks and Netlify functions. Warning: magic may happen here :-)

When you work with multiple workflow steps it's much easier to understand the publishing process when you visualize them in a diagram.

The Gatsby and Next.js feature development race is nice to watch if you’re a React developer, but what about our Angular friends?

The error from last time was resolved - explanation in the first few minutes. The rest of the stream we focused on generating PDFs using Statiq.

The Jamstack is a modern approach to building websites and apps, delivering better performance, higher security, lower cost of scaling, and a better developer experience. However, with so many tools to choose from, it’s easy to feel overwhelmed.

Last time we built a Hello World site, but the connection to a headless CMS left us with an error. This time we'll focus on debugging it and getting the content into the static site.

A lot of people think Jamstack is tied with Javascript. So can you make a Jamstack site without JS knowledge?

Everyone talks about webhooks and it became a buzzword. So is it just a simple HTTP request or are there some other specifics?

What is the Jamstack that you read everywhere? Is that an abbreviation of something? Everyone seems to know.

When we are considering which framework to use for new web projects, we tend to prefer the tools we know regardless of how suitable they are. So I tried the opposite.

You get excited about a product only to find out you need to fill in your credit card details in order to sign up. Or you can use it for free with one exception—the feature that got you excited in the first place. Conditions, rules, exceptions... enough. What if developers actually designed a free headless CMS plan for themselves? 

In the times of monolithic systems, it was crucial to pick the right system at the beginning. That decision inevitably locked you with a single vendor for years. Nowadays, in the microservices era, vendors claim itʼs easy to switch between their systems. Letʼs take a look at what “easy” means when switching your headless CMS and whether that decision could cost you your job.

The microservices approach promises easy switching between services and claims to enable you to use the best-of-breed tools. Is this true? How hard is it to switch a headless CMS that powers your website?

What is Sourcebit? How does it work and how does it make Jamstack website implementation easier? Should you use it for your next project?
I aim to answer these questions during my presentation about Sourcebit. I explain how it tries to unify the relationships between headless CMSs and static site generators.