Template engines
There are currently three template engines for trillium. Although they are in no way mutually exclusive, most applications will want at most one of these.
Askama
Askama is a jinja-based template engine that preprocesses templates at compile time, resulting in efficient and type-safe templates that are compiled into the application binary. Here's how it looks:
Given the following file in (cargo root)/templates/examples/hello.html,
Hello, {{ name }}!
use trillium::Conn;
use trillium_askama::{AskamaConnExt, Template};
#[derive(Template)]
#[template(path = "examples/hello.html")]
struct HelloTemplate<'a> {
name: &'a str,
}
fn main() {
trillium_smol::run(|conn: Conn| async move { conn.render(HelloTemplate { name: "world" }) });
}Ructe
Ructe is a compile-time typed template system similar to askama, but using a build script instead of macros.
- crate: https://crates.io/crates/trillium-ructe
- repository: https://github.com/prabirshrestha/trillium-ructe
- docs: https://docs.rs/trillium-ructe/latest/trillium_ructe/
Tera
Tera offers runtime templating. Trillium's tera integration provides an interface very similar to phoenix or rails, with the notion of assigns being set on the conn prior to render.
Given the following file in the same directory as main.rs (examples in this case),
Hello, {{ name }}!
use trillium::Conn;
use trillium_tera::{TeraConnExt, TeraHandler};
fn main() {
trillium_smol::run((TeraHandler::new("**/*.html"), |conn: Conn| async move {
conn.assign("name", "hi").render("examples/hello.html")
}));
}Handlebars
Handlebars also offers runtime templating. Given the following file in examples/templates/hello.hbs,
hello {{name}}!
use trillium::Conn;
use trillium_handlebars::{HandlebarsConnExt, HandlebarsHandler};
fn main() {
env_logger::init();
trillium_smol::run((
HandlebarsHandler::new("./examples/templates/*.hbs"),
|conn: Conn| async move {
conn.assign("name", "world")
.render("examples/templates/hello.hbs")
},
));
}