Sample article
From document to website
A look at the editable document, MCP authoring and static compilation that shape Lacuno’s workflow.
Lacuno starts with a structured document. Pages, nodes, styles, components and collections stay explicit, so a visual interface and an automated collaborator can work with the same material instead of translating between private formats.
MCP exposes that document through versioned operations. A client reads the current revision, proposes or applies a defined change, and receives structured errors if the document moved or the operation is invalid. This starter site was authored through that route, which makes the workflow concrete rather than aspirational.
The compiler turns the document into static pages. Static output keeps the delivery side small and portable: the result can be served from common hosting infrastructure, inspected in a browser and moved with the rest of the project.
The browser builder is planned and is not presented here as an available service. Today, this sample article demonstrates the content model and the path from a native Lacuno document to a working website.