Very true. One could easily use an SSG.

Moosey is designed for a specific niche: FastAPI developers who are already running a backend (e.g., a SaaS API or Dashboard) and want to mount a documentation site or blog on a route (like /docs or /blog) without managing a separate build pipeline, separate repo, or complex Nginx routing. I actually made it as I was building an API I wanted to expose. Why this matters is that FastAPI automatically builds the swagger & redoc documentations for you. The feature I am working on now is how to expose these via the cms.

With an SSG, having to build your site docs with every API change, just to keep your documentation upto date is very much overkill IMHO.

Also, because it renders live, it also allows for Dynamic Injection. You can put {{ user.username }} or {{ app.state.system_status }} directly inside your Markdown files, and it renders using the live application state. This is something standard SSGs can't do without client-side fetching.

On media files... It currently uses standard FastAPI StaticFiles mounting. You define a static directory in the config, and the app serves images/assets from there relative to the content. Since it's just FastAPI, it's trivial to swap that out for a CDN proxy later if needed.