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.
The original Lumen is built with Gatsby and connected to Kentico Kontent headless CMS. The site is already running, but some styles are missing as they were hard-coded in components. Uhh. Let's fix that and see where that takes us...
I managed to update the menu component to use the new version of the Gatsby source plugin for Kentico Kontent. It's a bit of recursive thinking, may need to adjust the implementation in the future, but it works for now.
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?
One of the reasons we create JAMstack sites is because of their great performance. Serving static files is easy and quick. But what if we upgrade the visitor's experience and make the site available offline?
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.
Everywhere you look, you see the word “Jamstack.” So you’ve probably thought about building a site using a static site generator. But where do you start? How do you choose the right framework for you and your team?