rfc VS Gatsby

If you're interested, we'd love you to checkout some of the features we're working on currently https://github.com/appwrite/rfc

If you're curious about what's next for Appwrite, or have a great idea, head on over to our RFC repo for more details.

We have just added a new draft for an RFC that will also refer to 2fa, so it should be expected. https://github.com/appwrite/rfc/pull/31

We hope you enjoyed this article! We love contributions and encourage you to take a look at our open isuses and ongoing RFCs.

That's not all! To get all the details on Appwrite 0.8, check out all the changes in the changelog on GitHub. Are you curious about the big ideas we have up next, or have a great idea for Appwrite's future? Check out the RFC Repo for more details. Also, our awesome-appwrite repo keeps growing with new tutorials, videos, and demos.

Currently we use MariaDB under the hood. But we have an RFC in place to be agnostic to the database and build adapters allowing users to use any database of their choice https://github.com/appwrite/rfc/pull/21

If you’re excited about this release, you should probably also track what is coming up next by visiting our Github projects. You can also ask for new features on our Github issues and go over our upcoming feature specs on the Appwrite RFCs repository.

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.