HTMLX FLOW DOCUMENT

A browser-native brief that reflows by default

Flow documents are the default OpenWebDoc profile: readable HTML, local assets, explicit metadata, and validation without a fixed canvas.

Why this profile exists

A long-form document should behave like the web. Paragraphs, tables, and lists should adapt to the reader's viewport before any runtime adds editing controls.

Readable first

Open the unpacked index.html and the document remains useful.

Package-local

Styles, metadata, and assets travel with the package and pass validation.

Agent-ready

Large edits happen in package files, then return through the CLI validator.

Canonical workflow

Flow document package operations
Step Surface Purpose
Read Browser Use the HTML document without app chrome or fixed-stage assumptions.
Revise Unpacked package Edit HTML, CSS, metadata, and declared assets directly.
Validate htmlx CLI Check paths, resources, security policy, and metadata boundaries.

Boundary with visual profiles

Fixed-stage documents and slide decks are still HTMLX packages, but they declare their geometry explicitly. Flow documents stay reflowable and avoid stage coordinates.