It’s founded in Rust and incorporates a Deno runtime for extensions.
It’s headless now, via JSON-RPC. I’ve got the basics of a trait based system which will enable different frontends. At the moment, I’ve created an extension for `pi` which allows me to use that as the frontend.
It's inspired by Zola, but has better documentation and will hopefully be more approachable when all is said and done. I'm trying to incorporate WebAssembly, with Yew, to give "islands" for high performance stuff you might want where WebAssembly makes sense. For example, I wrote search from the ground up, and built a search widget using Yew.
You can also just write JavaScript if you want.
It's a total work in progress, but I'm enjoying what I've built so far.
About an hour ago I was dismissed as AI slop on the r/rust Reddit. Whatever.
This tool is my line of defense in case `trunk` goes dead, which it seems to be increasingly likely. It helps me build fullstack sites using Actix Web and Yew.
Using it now to see if I can re-invent my blog site for the umpteenth time. :)
Compared to the majority of what I read below, I'm a rank amateur and have no right to post.
I'll do it anyway, as I need to learn to own where I'm at and have a backbone. :)
I'm learning the Zola static site generator and using to to build my blog at https://jeff-mitchell.dev. The focus is my mis-adventures learning the Rust language.
I've found it a challenge to get off my feet with Zola, but I'm slowly figuring things out. Little victory this evening, finally figured out how to get images linked in posts to render properly.
It’s founded in Rust and incorporates a Deno runtime for extensions.
It’s headless now, via JSON-RPC. I’ve got the basics of a trait based system which will enable different frontends. At the moment, I’ve created an extension for `pi` which allows me to use that as the frontend.
reply