Thinking of rewriting my daily puzzle site in Rust – seeking architecture advice

Hi Rustaceans, I run a minimal daily puzzle site called Minute Cryptic (https://minutecryptic.online/). It serves one cryptic crossword clue per day, with a progressive hint system and a short video explainer – no accounts, no database of users. Currently it's built with a lightweight JS stack, but I'd love to explore a Rust rewrite, mostly for the learning experience and to see if I can make the serving costs absurdly low. The core challenge: One new clue daily, with structured hint data and a video URL A hint state that's tracked per visitor (currently just localStorage) Zero user accounts, zero tracking What I'm trying to figure out: Framework choice – For a site this simple, would you reach for Axum + Askama, or is something like Leptos overkill? I don't need SSR or hydration; static HTML with a tiny API feels right. Content management – I could store clues as static Markdown files and embed them at build time, or use a small SQLite database. In the Rust world, what's the idiomatic way to handle a slowly growing collection of structured daily content? Deployment – I'd like to run this on a single cheap VPS or even a serverless edge. If you've deployed a similar Rust-based microsite, I'd love to hear about your setup. I'm not trying to over-engineer this, but I figure a rewrite is a great excuse to really learn Rust in production. Any pitfalls I should watch out for? Or examples of similar "one-post-a-day" sites written in Rust? Thanks, and if you want to see the current version for context, it's at the link above.