jquery-localize VS pongo2

I love static site generators and I really wish more sites were built with them. There are likely millions of websites that have no login functionality or other functionality that specifically requires a back-end, but use a CMS anyway. Usually a CMS is slower for the users on the site, more expensive for the company running it, less secure, less stable, and more maintenance than a statically generated site.

I do think there's still plenty of room for improvement for static site generators though. Does anyone have any recommendations for an SSG with easy support for multi-lingual websites? Ideally, I'd be able to translate the text and provide alternative images, videos, and links without having to change the HTML structure of a given page for each language. Technically, this can be done easily with JavaScript by using a plugin like jQuery Localize [1], but that has two major downsides: (1) all other languages except the default breaks if JavaScript is disabled and (2) users won't know that the site supports their language from search engine results (the snippet will be in the default language.) So it'd be great if I could write the pseudo HTML of a page once, but generate multiple HTML files for each different language (placed into their respective directory, e.g. en/, es/, fr/ etc.)

[1] https://github.com/coderifous/jquery-localize

I've used https://github.com/flosch/pongo2 since it feels more dev friendly (like almost every other framework I've used). Check out https://github.com/avelino/awesome-go#template-engines for some others.

Doesn’t it bother your that your templates aren’t really valid HTML? Because of the way html/template works, one isn’t really able to implement template inheritance properly. So you end up with opening and closing tags scattered around multiple files? You might want to look at Pongo2, which implements most of Django’s templating syntax (incl. inheritance) and is pretty stable: https://github.com/flosch/pongo2

At least template-wise, I've developed pongo2 mimicking Django's template engine which I use myself for various projects. For the rest I usually stick with the standard library (net/http), golang-jwt, the Gorilla toolkit (note that it's been archived recently) and some software architecture patterns for middlewares, database abstraction, etc.

pongo2 is a community-built template engine with syntax inspired by Django-syntax. It is built by the community for Go. It is very popular today, with more than 2K stars on GitHub.

Django uses Jinja templating engine. Something similar is available at https://github.com/flosch/pongo2 Now you just have to pick which router you want and which ORM or not-ORM.

Yes, Go templating is quite hard. There was a feature request[1] to implement the Django/Jinja2-like Pongo2 template engine[2], but got rejected because it would have been a too big change.

[1]: https://github.com/gohugoio/hugo/issues/1359

[2]: https://github.com/flosch/pongo2

Yes, there is pongo2 [0] and my runner (basically a small Go software that runs the template engine) pongo2-runner [1].

I'm not the author of the library (pongo2), but I'm using pongo2-runner to dynamically create config files out of environment variables, with custom logic. Super recommended.

[0]: https://github.com/flosch/pongo2

[1]: https://github.com/swisscom/pongo2-runner