Weblate VS Gatsby

For translations I can recommend you to use sites such as Crowdin, OneSky, Transifex, Weblate. Lot of smaller (singe or small team) developers are handling translations with the help of their users. You would be surprised how easy and how fast it is to manage translations at no (or nearly) cost this way. There is a lot of users willing to help to translate the app to their native languages.

weblate.org — It's free for libre projects up to 10,000 string source for the free tier, and Unlimited Self-hosted on-premises.

WebLate (their projects dashboard)

I'm using weblate.org. It's open source so it made the most sense to me to use for an open source Android app. It can also be used for free. It's not trivial to use but can be managed.

if the author of the app use a public translation service like https://weblate.org/ or https://crowdin.com/ you can do it via web browser.

For translation, using a Weblate instance makes a lot more sense over using Google Sheets https://github.com/WeblateOrg/weblate

hosted.weblate.org is only free for open-source projects, but it shouldn't be hard to find alternative hosting, or launch a Docker container in the cloud??

If there is not any, i can recommend Weblate, which is open source translation platform and hosting is free on their side for open source projects, or you can also self-host it.

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.