Writing in Markdown is the nicest way to blog - plain text, no fiddly editor, portable forever. But most Markdown blogging setups (Jekyll, Hugo, Eleventy) put a build step between you and publishing: write the post, run the generator, deploy the output. It is a small friction, but it is enough to make you not bother on a busy day.

You can keep Markdown and drop the build step entirely.

Write, save, live

With a render-on-request engine, publishing a post is just: add a Markdown file, and it is live. The first visitor triggers the render; the result is cached; every later visit is a fast static page. Edit the post and it refreshes. There is no generator to run and no deploy pipeline to wait on.

What you still get

• Clean Markdown - front matter for the title, date and summary; the body in plain text.
• RSS and Atom feeds - generated from your posts automatically, so readers and aggregators can subscribe.
• Fast pages - cached static HTML, good for readers and for search ranking.
• Portability - your posts are files; keep them in git, move them anywhere.
• Dynamic extras when you want them - a comment form, sign-in for members-only posts, even pay-per-read - without a separate backend.

No pipeline, no lock-in

Because there is no build artifact and no platform database, your blog is never trapped. It is a folder of Markdown you own, served by a small engine. Switch tools and your posts come with you unchanged.

Start writing

lazysite serves Markdown as live pages with feeds built in - a blog with no build step and no database.

• See why the build step is optional.
• Read about publishing by voice for hands-free posts.
• Or get started.