Let's explore how to create beautiful animated gradient texts (like on Vercel.com) with plain HTML and CSS! This is an interactive blog post with bespoke widgets designed and implemented to help you understand all the key concepts much faster!

We're going to implement an animated emoji by morphing SVG paths. (It sounds fancier than it should.) The code itself is going to be pretty straightforward but we'll need to spend some time in a graphic editor (like Figma) to get our SVG ready.

In this blog post, we'll dive deep into what "any" and "unknown" types are, what are their similarities and differences, and when (not) to use them.

In this article, you're going to learn how to create a custom animated (yet accessible) checkbox. The technique that you'll learn is also applicable for styling radio inputs.

We're going to implement a shild checkmark animation by animating lines in SVG (the path element) and we'll learn how to extract animation logic into re-usable custom hooks.

You'll learn how to create this SVG animation in React Spring and what's tricky about animating transform: scale(...) and transform rotate(...) in SVG.

You'll learn how to build SVG animations using React and the React Spring library.

What is blocking fallback in getStaticPaths and when it should be used?

In this article we'll explore the pros and cons of server-side rendering as opposed to "client-only" single-page apps (and statically generated sites). We'll go through the UX 📱, business 🧳, and product development 👩🏿‍💻perspectives. You'll learn when you should opt for server-side rendering, when statically generated sites are a better choice, and under which circumstances you'll be better off with a "basic" SPA.

In this series of articles, I'm going to go through the _what_, _why_, and _how_ of the migration process of our React web application 💻 to a server-side rendering solution. You'll learn what SSR is, how it differs from the "client-only" single-page applications and "regular" web apps, what are its pros and cons, and, finally, how to go about **migrating an existing React app to an SSR solution (Next.js).** (The concepts are the same for Vue apps (and Nuxt.js) or similar. 😉)