Document structure

Document

Top-level print intent wrapper for a complete semantic document. It does not synthesize pages or own document data.

Elementef-print-document
CapabilityP0 portable
Maturityimplemented
Pagination ownerBrowser / selected renderer

Capability note. Page size and margin are currently stylesheet-level tokens; the wrapper itself does not create a synthetic page model.

Example 1

Quarterly report

A complete report shell with ordinary semantic headings and body content.

Open standalone print preview

On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.

View HTML
<ef-print-document>
  <header>
    <p class="folio-kicker">Quarterly review</p>
    <h1>Operational Readiness</h1>
    <p class="folio-meta">Prepared 22 September 2026</p>
  </header>
  <hr class="folio-rule">
  <main class="folio-stack">
    <section>
      <h2>Executive summary</h2>
      <p>Folio keeps document meaning in ordinary HTML while reusable print primitives express layout intent.</p>
    </section>
    <section>
      <h2>Decision posture</h2>
      <p>The browser or selected renderer owns pagination.</p>
    </section>
  </main>
</ef-print-document>
Example 2

Decision memo

A compact memo using the same document wrapper without a page-layout runtime.

Open standalone print preview

On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.

View HTML
<ef-print-document>
  <article class="folio-stack">
    <p class="folio-kicker">Decision memo</p>
    <h1>Renderer capability policy</h1>
    <p class="folio-meta">Owner: Platform Engineering</p>
    <div class="folio-callout">
      <strong>Decision.</strong> Use explicit P0–P3 capability tiers rather than hiding renderer differences.
    </div>
    <h2>Rationale</h2>
    <p>Mainstream browsers do not expose identical paged-media features.</p>
  </article>
</ef-print-document>
Example 3

Technical handoff

Semantic lists, code-like metadata, and status content remain ordinary HTML.

Open standalone print preview

On narrow screens the embedded example uses a screen-only inspection layout. Printing and the standalone document keep Folio's physical print rules.

View HTML
<ef-print-document>
  <main class="folio-stack">
    <p class="folio-kicker">Engineering handoff</p>
    <h1>Print pipeline</h1>
    <p>Required verification:</p>
    <ol>
      <li>Wait for document assets.</li>
      <li>Select the declared renderer profile.</li>
      <li>Export or print with known settings.</li>
    </ol>
    <p class="folio-meta">Core layout stays standards-first and framework-independent.</p>
  </main>
</ef-print-document>