react-coding-challenges VS Gatsby

15-) You have completed your studies and want to test yourself with the project. Here are a few examples of projects by difficulty level. react-coding-challenges

I've had a couple of frontend interviews that involve literally z e r o Leet Code questions. Instead they're more practical, live React coding challenges. I'm looking for more resources to practice. Something along the lines of this or the hacker rank react test.

A collection of react challenges (https://github.com/alexgurr/react-coding-challenges)

There is a little exercise I was asked to do recently as part of a skills assessment, and it used the Spotify API. It’s not a bad way to practice: https://github.com/alexgurr/react-coding-challenges/tree/mas...

We used https://github.com/alexgurr/react-coding-challenges for the live coding test and it worked well enough.

React Coding Challenges

Take a look at the new challenge template here and what makes a good challenge.

It sure is! https://github.com/alexgurr/react-coding-challenges#contributing

The challenges

I currently maintain a GitHub repo called react-coding-challenges. It involves a variety of different difficulty challenges people can check out and complete. I also have a separate, private repository for the solutions to these challenges. The solutions are invite-only, meaning I need to invite each person as a collaborator before they get access (see the why here).

The first time I started building static websites is when I discovered Gatsby. I built several projects using Gatsby and hosted it on Netlify free tier. It felt like a really robust architecture and I loved that it was free.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.