simplelocalize-cli VS gutenberg

shamless plug You can use my app for that, it doesn’t require monthly subscription. 😉

In favor of typesafe-i18n: - Offers an option for asynchronous loading of locales. It's in the roadmap for i18nifty but as of today it doesn't features it. - It's lighter 1.3Kb vs 22Kb for i18nifty (I could work on reducing the size but it isn't high in my priorities). - Support third party localisation services such as https://locize.com/ https://lokalise.com/ or https://simplelocalize.io/.

NextJS, a well-known framework among React developers, provides multiple libraries that create a very developer-friendly environment. The most popular ones are i18Next, next-translate and, our main focus in this blog post, next-18next, a translation library that does a fantastic job helping in translation management. The following blog post will show you how to set up next-i18n in your NextJS app and manage translations with SimpleLocalize. Take a look at our demo app for the reference.

own SaaS my salary is now higher than before 😌

I know the advantage of this approach is that you can do it for free, but in general you could also use something like SimpleLocalize (I’m the author, backend uses Spring and Java 18😎) You can keep translations there, auto-translate and host them on CDN. In my approach, the cool thing is that you can fix the incorrect auto-translated texts in the editor. It supports DeepL and Google Translate, there is a free forever plan and free 14-day trial.

Wow, that’s great! I was thinking that you used some kind of software like SimpleLocalize to use auto-translation. :)

Don’t implement it on your own. Use something like SimpleLocalize and use their REST API and CDN. Client will have a nice panel to edit/change translations and you will get a nice API to fetch translated content.

So after shopping around a bit I found a simple, dependency-less static site generator called Zola. The lack of dependencies sounded very attractive after all the headaches trying to update my Gatsby modules. I wanted to give Zola a try and see what tradeoffs I would need to make coming form a React-based framework to this Rust-based generator.

I think you're thinking about Zola: https://github.com/getzola/zola

But yes, if I were to recommend something, it'd be Zola given that there's just one executable that you need to run and there's absolutely no setup required.

If I were to start again from scratch, I'd likely use Zola as SSG (https://www.getzola.org/)

I've used Zola (https://github.com/getzola/zola) for a static project homepage a few years ago to showcase examples with a simple description and a wasm app embedded in the page, it worked perfectly for me and the docs was clear on how to use it. It was very easy to set up along with a GitHub action to automatically update the wasm binaries when needed. It is definitely a tool I keep in my mental toolbox as a good default.

I'm currently learning https://www.getzola.org/.

It's more manual than idy like but it's gonna be for a small personal and work website so I don't mind much.

It's super fast.

Doesn't seem to fit your use casr but still.

(Note: that list is overwhelming; you don't need to go through it. Order by popularity and look at the top 3-5 at most. Hugo, Jekyll, Gatsby... Personally I'm using Zola [ https://www.getzola.org/ ] for a couple of sites, but that's just me.)