Publish your notes as static websites. It takes Markdown notes from any folder, selects the ones marked for publication, injects them into a site repository, builds a Docker image and pushes it to your container registry.
https://gramr.smoowy.fr
- Rust 99.4%
- Dockerfile 0.6%
| docs | ||
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
| rustfmt.toml | ||
gramr
Publish your notes as static websites.
gramr takes Markdown notes from any folder (an Obsidian vault, a Logseq graph or plain .md files), selects the ones marked for publication, injects them into a site repository, builds a Docker image and pushes it to your container registry.
gramr publish blog # select, build, push
gramr publish blog --dry-run # show what would be published
Status: early development, not usable yet.
Principles
- Opt-in publishing: a note is published only if its front matter says so.
- Generator-agnostic: Zola, Hugo, Astro… if it builds in Docker, gramr can publish it.
- Content and presentation are separate: notes stay in your folder, and the theme and templates stay in the site repository.
- The image is the boundary: gramr pushes an image and stops. Deployment is up to you.
Requirements
- Git
- Docker with Buildx
Documentation
- Overview: what gramr does and doesn't do, philosophy, how it works.
- Getting started: from nothing to a published site.
- Guides: writing notes, unlisted pages, previewing, deploying.
- Reference: commands, configuration, front matter, errors.