Writing for lazysite is just writing Markdown. There is no build step and no database: drop a .md file into the site, and it is a page.

Create a page

Save a file anywhere in the site, for example guide.md:

---
title: My Guide
subtitle: Getting started
---

## Hello

This is a **lazysite** page, written in Markdown.

Visit /guide and it is there. The first request renders the Markdown to HTML and caches it next to the source; every request after that is a plain static file. The block at the top, between the --- lines, is front matter - the page's metadata.

URLs come from file paths, without the extension:

index.md          ->  /
about.md          ->  /about
docs/install.md   ->  /docs/install

Always link with extensionless URLs - /about, not /about.html.

Ways to edit

Change a file and save - that is the whole workflow. Pick whichever way in suits you:

• The manager - a menu-driven browser interface, the easiest way for people. See Configure with the manager.
• On disk - any text editor, then your normal git flow.
• WebDAV - mount the site and edit files directly.
• The control API - publish programmatically from a script or another system. See API and raw mode.
• The AI connector (MCP) - let an assistant such as Claude publish through first-class tools. See AI connector.

A saved edit re-renders on the next request - nothing to rebuild, nothing to deploy. Those are the ways in; what you write is the same whichever you choose.

Write the content

Standard Markdown works as you would expect - headings, lists, links, bold, code, tables, block quotes. Two lazysite touches:

• Headings start at ##. # is reserved for the page title (it comes from the front matter), so your sections begin at level two.
• Fenced divs wrap content in a styled container without writing raw HTML:

<div class="callout">
<p>This becomes a styled box.</p>
</div>

That renders as <div class="callout">...</div> for your theme to style.

Where to next

• Front matter - the metadata keys you can set on a page.
• Advanced authoring - the full set of capabilities by topic: dynamic variables, content includes, remote sources, page scans, feeds, forms, JSON data, caching and more, each on its own page.
• Reference - configuration keys, template variables, and file locations.