handlebars-rust VS jamstack.org

handlebars to create the HTML templates of all the built-in components

handlebars-rust, based on Handlebars

Handlebars/guide/#what-is-handlebars)

filling out templates inside files using Handlerbars

Would Handlebars-Rust be good for parsing non-Rust files? Or is there another templating engine built in Rust that I should use?

I am learning Rust currently, so to improve my skills, I am considering using its Handlebars implementation.

If you paid attention to the function code above, it might have occurred to you that the assets we serve don't have to be completely static. For example we could instead embed a handlebars template or similar & render it with the handlebars crate, allowing us "semi-dynamic" content for lack of a better name.

Tera is a templating engine, inspired by Jinja2 and Django. There are other options like handlerbars and askama, but in this case I prefer to use tera because I'm familiarized with the syntax.

This weekend I learned some unfamiliar behaviors with the way Handlebars handles nested variable scopes. I typically use Handlebars via the handlebars-rust implementation which aims to maintain nearly one to one compatibility with the JavaScript implementation. They have block scope helpers such as #each and #with, both of which create an inner scope for variable resolution. Unfortunately, the syntax can be quite unintuitive for accessing outer scope once in those nested scopes.

I have been tweaking and fixing issues with newline stripping feature for handlebars: https://github.com/sunng87/handlebars-rust/pull/448/files

Docusaurus is a Jamstack SSG (Static Site Generator) mainly intended for documentation and blog websites. It is a Meta Open Source project. Its configuration is done mainly through a JavaScript file called docusaurus.config.js.

Netlify has gained popularity among developers for its ease of use and powerful features. It's a great option for hosting static websites or Jamstack applications.

Jamstack Org

Jamstack architecture continues to gain popularity as a modern web development approach that focuses on pre-rendered content served from a CDN. Some benefits of Jamstack include better performance, lower cost, and greater scalability. Expect to see growth in Jamstack frameworks like Gatsby, Next.js and Nuxt.js in 2023.

More importantly, Netlify, the creator and stewards of the term Jamstack including it's canonical site, has largely abandoned the term as well, in favor of a "composable web" term that better aligns with their ambitions around becoming a broader enterprise platform including content (with tools like Netlify Connect).

I have been using the hosting environment provided by Netlify for years. I am aware there are several available including Vercelli and Heroku, to name a few, but Netlify was the first I tried and it continues to work well. It links into my Git repos on BitBucket and also offers Functions-as-a-Service (FaaS) for experimentation and small projects. Netlify is also a prime advocate of the JAMStack architecture that is gaining considerable interest.

You should check out JamStack. The premise is that the majority of your site is static content and you can push it out to CDNs that are frequently cheap or free.

Perhaps this is worth checking out and utilizing when I have the time to attempt another JAMstack project. Possibly Eleventy?