lazysite
Markdown-driven static pages for any CGI-capable web server. No build step, no database, no CMS.
What it is
Drop a .md file in your docroot and it is served as a fully rendered HTML page. The first request generates the HTML and caches it alongside the source file. Every subsequent request is a plain static file — no process, no overhead.
Write content in Markdown. Design the site in a Template Toolkit layout file. The two never touch each other.
This site is its own demonstration. The pages are `.url` files — lazysite fetches the Markdown from the [GitHub repository][github] and renders it on first request.
Where to go
- Readme
- Installation, requirements, configuration, troubleshooting, and technical internals. Start here if you are setting up lazysite on a server.
- Authoring
- Writing pages — front matter, Markdown, Template Toolkit variables, fenced divs, remote sources, and cache management. Start here if you are building or maintaining a site.
Key features
- No build step
-
Write a
.mdfile, save it, it is live. Delete the cached.htmlto republish after edits. That is the entire workflow. - No database
- Files are the source of truth. Nothing to back up separately, nothing to migrate.
- Fast by default
- Dynamic only on the first request. Plain cached HTML is served after that — no interpreter, no overhead.
- Design and content separated
-
The Template Toolkit layout owns the site design. Content authors work only in
.mdfiles. - Version control ready
- Everything is a file. The entire site lives in a git repository.
- Remote sources
-
.urlfiles pull Markdown from a remote URL — a GitHub raw file, for example — and render it through the same pipeline. Documentation lives with the code; the site always shows the current version. - Content is portable
-
Plain
.mdfiles work with any Markdown processor. Switching tools does not mean rewriting content.
Licence
MIT. Source on GitHub.