HTML Documents

HTML is a general-purpose document type for anything that should be presented in a browser. It is not limited to a fixed template or use. Choose its information structure, design, and interaction based on the project's purpose.

What HTML can produce

Examples include:

• Designed documents and reports
• Product or service pages
• Screen concepts and prototypes
• Dashboards and status views
• Guides and explanatory material
• Pages that present data or research
• Presentation or demo material
• Other web-based project content

The list does not restrict the format. If a browser is the right medium, build the result around its real purpose.

Before creating one

Decide:

• Who will use or read it?
• What must it communicate or test?
• Which materials and decisions are authoritative?
• Is it mainly for reading, visual explanation, or interaction?
• Where and how will the finished result be used?

Avoid adding layout or effects that do not support the purpose.

Create with an Agent

Read the source-of-truth document and related materials in [project name], then create an HTML document for [purpose].

Add the intended tone, structure, content, and use when relevant.

Organize it for [target audience] so it communicates [key message] in [desired presentation style].

An Agent can create a complete HTML document or update an existing one. Inspect same-purpose documents before creating a duplicate.

Use project materials

HTML can use content from Markdown, File, Diagram, OpenAPI, and ERD documents in the same project. Structure the information for its audience instead of merely listing source material.

An HTML document does not become the project standard by itself. Reflect new decisions or changed facts in Markdown.

Review by purpose

Confirm accuracy, consistency with the current project standard, suitability for the audience, freshness of evidence, absence of secrets, and correct browser rendering.

For a prototype, emphasize user flow and behavior. For a report, emphasize content and readability. For an introduction, emphasize message and visual communication.

Update and share

Update the existing HTML when the purpose and content continue. Create a separate document only when another result needs to be preserved independently.

Before sharing, review the information, external resources, and public scope. Link decisions and follow-up work back to Markdown and Kanban.

When relationships or structure need a dedicated visual model, continue to Diagrams.