GEL VS handlebars-rust

Hey, cool! From my brief look at your link, I didn't catch how you're storing your triangulations, since only data structures for points and lines and such are mentioned. Do you have a mesh data structure? I'm thinking of something like a half-edge based representation, as found in GEL. That would be really cool to have in Rust.

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