Just run `marmite` on a folder full of markdown files and get a full website/blog running in seconds.<p>"I'm a big user of other SSGs but it is frequently frustrating that it takes so much setup to get started.
Just having a directory of markdown files and running a single command sounds really useful.
— marmite user."
[offtopic]
I just noticed that my original post title has been edited (not by me) and the part where it said `written in Rust` has been removed.<p>I see other posts on the page showing `built with Python`, `Python based`, why `written in Rust` was not allowed? just curious.
I did something similar a few months ago in python.
One notable difference is that I got rid of the frontmatter, instead I use the commits history to find the creation and update dates of posts.<p><a href="https://github.com/HenriTEL/gitblog2">https://github.com/HenriTEL/gitblog2</a>
I really like it.
I have been on a quest to find very simple ssgs such as this.
I have been trying to out Zola, as mentioned in the readme, but I really want to make sure there aren't things like telemetry or other random features injected in or getting added (as seems to be the case with jekyll with ai-folio or academic pages) so it takes a while to go through everything.<p>Ai-folio or academic pages is basically my use case or target, but I want something with zero javascript, which tends to be a bit hard in todays age.
> cargo install marmite<p>I'm not the only one (1) that believes this is wrong direction for cargo, and is abusing it's intent and purpose.<p>If you want to distribute an application, there are lots of ways to do that. If it's a developer tools, for developers, `cargo install` might be suitable, sure... but I think there's a fair argument to be made that if you want a tool:<p><pre><code> git clone foo
cd foo
cargo install --path .
</code></pre>
Is an explicit, safe and less error prone way of doing it.<p>...and one that doesn't walk us down the road of (see the linked thread) the obvious desire people are going to have sooner or later to cache binary builds instead of building locally, and turn `cargo install` into some kind of binary application distribution application or app store.<p>If you don't believe me, read that thread, and the linked thread.<p>[1] - <a href="https://github.com/rust-lang/cargo/issues/13994#issuecomment-2143204956">https://github.com/rust-lang/cargo/issues/13994#issuecomment...</a>