From Markdown to a page worth sharing
Fictional sample. Every metric, status, organization, and decision on this page exists only to demonstrate the report engine; replace it with verified project evidence before use.
Give an agent a declarative source, not a frontend project. Build reports, research, architecture notes, tutorials, dashboards, and landing pages that open directly from disk.
Start with the work, not the framework
A Portable boundaryThe source remains declarative and the package owns rendering, interaction, confinement, and offline output.View full definition keeps the opening thesis in normal reading flow while making the page's main claim easy to scan.
Write naturally
Use Markdown, frontmatter, confined partials, and local assets.
Add intent
Choose package-owned cards, decisions, interactions, diagrams, timelines, and charts.
Ship static output
Build through one production path that validates before it writes.
The path to a useful page
Select a starter
Pick the page shape closest to the reader's job.
Replace the sample evidence
Keep the semantic structure and make the content factual.
Compile locally
Create one file or a content-addressed directory.
Review the artifact
Exercise the real page at desktop and mobile widths through
file://.
Proof without a hidden service
Keep the public format data-only
The package owns rendering and interaction behavior so authors do not need JSX, CSS, callbacks, or a hosted editor to finish a page.
Portability details
Opening directly from disk proves that the artifact does not depend on a development server or remote page runtime after compilation.
Build the first page
agentic-report init ./my-page --starter landing
agentic-report build ./my-page --output ./my-page.htmlUse validate or inspect later when focused source diagnostics would help.
What stays outside the source format
Remote fetching, raw HTML, executable templates, arbitrary plugins, and author-supplied browser code stay outside the portable trust boundary.