scaffold-eth VS Gatsby

If you want to learn to develop apps for the EVM (Thats Ethereum, Polygon, xDai, Aurora and many others) then you should read through the code in the various branches of https://github.com/austintgriffith/scaffold-eth for really good full-stack examples

git clone [https://github.com/austintgriffith/scaffold-eth.git](https://github.com/austintgriffith/scaffold-eth.git) challenge-2-token-vendor cd challenge-2-token-vendor git checkout challenge-2-token-vendor yarn install

In this blog post, I’m going to cover the first scaffold-eth speed run project: creating a Staking dApp. If you want to know more about scaffold-eth and my current journey in the web3 world you should read my previous article: My journey in Web3 development: scaffold-eth.

https://github.com/austintgriffith/scaffold-eth is a great ethereum boilerplate project that uses yarn workspaces in a monorepo, its a pretty standard practice that I've seen in the NFT/blockchain dev space.

I'm a fullstack JS developper, i've working and looking heavily into building on ethereum, so this is my first dive into the space. I would love some feeback from more senior devs on this, on the React and Dapp part. It is heavily based on scaffold-eth (and some Uniswap-interface code reading) so I'd recommend starting there if you're starting out rather than my starter, the docs and content there are first class. The stack is just the stack i am used to working with: Tailwind UI, Typescript and Redux Toolkit, and more. I'll be adding more examples other than the Greeter soon. Also i am for hire if you're looking for junior Dapp devs :) Thank your for your time !

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.

Both Chakra UI and Shadcn supports reusable components and can be used with different frameworks like React, Gatsby, Next etc.