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?

Are you just starting out with Vue.js? Or has it been long since you’ve worked with Vue? This cheat sheet lists the nine most common tasks and solutions when outputting data to HTML.

Do you need to animate multiple elements that are related to each other in Vue?

Whenever I'm starting with a new framework or it's been a while since I've used it, I always end up searching for the same simple things.

GitHub Actions allow developers to build Jamstack sites and deploy them to GitHub Pages. How can we trigger a build when content gets published?

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

In JavaScript, a debounce function makes sure that your code is only triggered once per user input. Search box suggestions, text-field auto-saves, and eliminating double-button clicks are all use cases for debounce.

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

Is your blog built using Next.js and you want to use syntax highlighting on code samples? This short guide will show you how to plug Highlight.js into your Next.js site.

Last week I was recording a presentation for the conference Kontent Horizons. I did not want to just use a webcam and laptop mic, so I had borrowed a Sony Alpha II camera.

These nice transitions between static pages that don't make your browser flick, do you have them on your website? No? It only takes an hour to set it up on a Next.js site. 

I stumbled upon a problem when resolving rich text data and images in Gridsome. The images were just not showing up.

Gatsby helps developers build blazing fast websites. But how fast is build time for the actual website itself? And how can one developer advocate help reduce build times for thousands of others?

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.

Stage files, add a commit message, push. No – wait! Not that file. And now we need to start googling.

There are so many great CSS resources all over the internet. But what if you just want a simple layout and you want it NOW?

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.

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?

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?

On average I work with JSON data 18 times a week. And I still need to google for specific ways to manipulate them almost every time. What if there was an ultimate guide that could always give you the answer?

We all know we should write unit tests. But, it's hard to know where to start and how much time to devote to tests compared to actual implementation. So, where to start? And is it just about testing code or do unit tests have other benefits?