Explanatory HTML Pages

Build one page that helps a defined reader answer a concrete technical question. Favor clarity over decoration: the page should teach a model, not advertise a product.

Contract

Input

• Technical concept: the system, term, mechanism, or workflow the reader needs to understand.
• Available project context: supplied files, documentation, product conventions, terminology, and constraints that are already available.
• Audience: what the reader knows, what they are trying to do, and the language level that will help them.
• Optional visual constraints: brand rules, colors, type choices, viewport range, print needs, motion preferences, or required diagram style.

Output

• A self-contained explanatory HTML page: semantic HTML with inline CSS, readable diagrams, and no required network access. Add JavaScript or local assets only when they materially improve the explanation.
• A concise handoff: the created path, chosen teaching structure, audience or language level, and any intentional dependencies. Include the parse result.

Default workflow