Semantic source first
Headings, tables, figures, lists, and links stay native HTML. Custom elements are reserved for reusable print/layout intent.
A standards-first print component system for professional HTML documents. Folio expresses document and pagination intent with semantic HTML, passive light-DOM elements, and print CSS while the browser or selected renderer remains responsible for physical pagination.
Folio makes page intent easier to declare without quietly becoming another browser layout engine.
Headings, tables, figures, lists, and links stay native HTML. Custom elements are reserved for reusable print/layout intent.
Page rules, breaks, columns, side rails, and print presentation remain standards-based and visible in the cascade.
Chromium-only margin boxes, deterministic export, and enhanced publishing features are never advertised as universal browser behavior.
Every registered Folio element has a dedicated page with three print-ready examples and its current evidence posture.
Top-level print intent wrapper for a complete semantic document. It does not synthesize pages or own document data.
P0 portable · implementedA document cover/title region that requests a page break after itself using native fragmentation.
P0 portable · implementedBlock-level section wrapper with explicit optional page-break intent before or after the section.
P0 portable · implementedTerminal document region for contact information, closing content, legal notes, or branded back matter.
P0 portable · implementedA semantic three-region document header that stays in normal flow portably and can express running-page intent without faking pagination. Slots name physical positions: left, center and right keep their edges even when a region is omitted or the document is right-to-left.
P0 in-flow · P1/P2 running capability · implemented / capability-boundA semantic document footer with three regions and explicit running-page intent while preserving a visible P0 fallback. Slots name physical positions: left, center and right keep their edges even when a region is omitted or the document is right-to-left.
P0 in-flow · P1/P2 running capability · implemented / capability-boundAn explicit page-counter intent marker that never estimates pagination from DOM height and keeps authored fallback text available.
P1/P2 counter · P0 authored fallback · implemented / capability-boundNative CSS multicolumn flow for report, editorial, and digest layouts that participate in browser fragmentation.
P0 portable · experiment-backedIn-flow main/rail composition using CSS Grid as the current side-panel candidate.
P0 candidate · provisionalAn out-of-flow artwork or watermark layer that sits behind semantic foreground content without depending on unsupported page-box backgrounds.
P0 element layer · experiment-backedExplicit native page-break intent without measuring the DOM or manufacturing synthetic pages.
P0 portable · implementedRequests that a bounded content block avoid internal fragmentation using native break-inside behavior.
P0 portable · implemented / best-effortA compact domain-neutral label/value/detail block for scores, counts, deltas, coverage, financial values, or other report metrics without calculating their meaning.
P0 portable · implemented / report-fixture evidenceA compact report-quality block for completeness, coverage, confidence, comparability, suppression, warnings, and limitations supplied by the consuming application.
P0 portable · implemented / report-fixture evidenceA structured evidence-oriented finding block that keeps observation, implication, possible action, and evidence-needed content distinct without inventing domain conclusions.
P0 portable · implemented / report-fixture evidenceA bounded emphasis block for decisions, warnings, evidence, and summaries using print-safe flow and keep-together intent.
P0 portable · implemented / cross-browser evidenceA print-aware wrapper around native figure semantics that requests caption cohesion without replacing figure, image, SVG, or figcaption HTML.
P0 portable · implemented / cross-browser evidenceA responsive screen container and print contract for native semantic tables, including repeated-header intent, row break avoidance, wrapping, and numeric alignment.
P0 portable · named-page behavior renderer-sensitive · experiment-backedA print-safe wrapper for native pre/code content with controlled monospace typography and wrapping that prevents long lines from clipping the page.
P0 portable · implemented / cross-browser evidenceA semantic contents wrapper for native navigation and lists, with authored page-number presentation in P0 and explicit separation from automatic target-page counters.
P0 authored pages · P3 automatic target counters · implemented / capability-boundAn in-flow annotation primitive for notes, caveats, references, and explanatory material without pretending to provide automatic footnote placement.
P0 in-flow note · P3 footnote/sidenote enhancement · implemented / cross-browser evidenceTutela assessment record preserving posture, scope, unknowns and evidence.
P0 portable · implementedPrints Tutela PASS, CONDITIONAL, BLOCKED or INDETERMINATE state.
P0 portable · implementedPrints an invariant and its evidenced state.
P0 portable · implementedPrints an evidence reference and provenance.
P0 portable · implementedMakes unresolved security knowledge explicit in print.
P0 portable · implementedPrints approved exception scope, controls and expiry.
P0 portable · implementedA dominant identity region (name, optional tagline) beside a compact contact region that stacks. data-contact="inline" wraps contacts in a row beneath the identity.
P0 portable · fixture-backedPrimary regions grow and wrap on the start side while one [data-row-end] region (dates, years, amounts) stays on a single line at the end of the first row. No fixed coordinates.
P0 portable · fixture-backedA repeated logical entry whose first child (usually an .ef-row header) keeps with the content that follows it. data-keep requests keeping a short entry whole.
P0 portable · fixture-backedA compact native list whose items may open with an emphasized lead phrase followed by regular-weight detail. Items request not to split across pages.
P0 portable · fixture-backedA native list rendered inline with a configurable separator after each item but the last. Wraps naturally with the surrounding text.
P0 portable · fixture-backedA label and its value laid out inline with a hanging continuation, typically a description list holding an inline collection.
P0 portable · fixture-backedGroups of a heading plus a compact list in auto-filled columns. Any number of groups and items; each group asks to stay whole across pages.
P0 portable · fixture-backedCompact block spacing and heading keep-with-next intent for dense professional documents, applied once on the document root.
P0 portable · fixture-backedDocument-root rhythm for dense long-form reading: justified, hyphenated paragraphs with first-line indents, heading keep-with-next, widow/orphan control, and optional lead-line small caps or drop caps.
P0 portable · fixture-backedA self-contained article or chapter inside a document or issue. data-start="page" begins it on a new page; data-start="recto" records right-hand-page intent. Article-local heading sizes are tokens.
P0 portable · recto P3 · fixture-backedOpening front matter on a native header: [data-kicker] article type, h1 title, [data-subtitle], contributors, affiliations, and metadata. Spans all columns when placed inside multicolumn flow and keeps with what follows.
P0 portable · fixture-backedNative list of contributors that flows inline with a configurable separator. Affiliation and correspondence markers are links to affiliation IDs, so the mapping does not depend on visual order; [data-orcid] links stay unbroken.
P0 portable · fixture-backedCompact list of affiliations with authored markers and a hanging indent, so long institution names wrap under their text. Items carry IDs that contributor markers link to.
P0 portable · fixture-backedGeneric label/value metadata on a native dl with div groups: DOI, dates, licence, citation, ISSN, publisher, version. Two aligned tracks by default; data-layout="inline" runs groups together. Long identifiers wrap.
P0 portable · fixture-backedRuled abstract block with a small-caps label. data-variant="structured" runs each part's h3 into its first paragraph (Background. …) while keeping real headings in the outline.
P0 portable · fixture-backedCaption for figures, tables, listings, or a table's trailing notes: an emphasized [data-label] (Figure 2., Table 1.), caption text, and block [data-note] and [data-source] lines.
P0 portable · fixture-backedDisplay equation on a native figure: consumer-supplied MathML, SVG, or HTML centered in a three-track grid with the authored number (figcaption) at the end. data-align="start" left-aligns multi-line equations. Kept together; stable id for cross-references.
P0 portable (MathML Core where supported) · fixture-backedFull-width material inside multicolumn flow: a figure, table, callout, or heading that spans every column, with column text continuing before and after it in source order.
P0 portable (column-span: all) · fixture-backedBibliography layout on a native list: hanging indent for author-year styles, or data-style="numeric" with authored [data-marker] labels in a hanging gutter. Long DOIs and URLs wrap anywhere; entries request keep-together.
P0 portable · fixture-backedAuthored in-flow notes on a native ordered list, with optional [data-backlink] links back to the reference point. Serves endnotes and note-style (notes-bibliography) citations.
P0 portable · footnotes P3 · fixture-backedBack-matter statements as sections with run-in h3 labels in compact type: acknowledgements, funding, competing interests, contributions, data and code availability, ethics, supplementary material. Each statement requests keep-together.
P0 portable · fixture-backedCommon document-flow and fragmentation primitives.
Static running content and Page X of Y where validated.
Controlled PDF generation and renderer diagnostics.
Optional advanced publishing-engine capabilities.
The original core primitive set is now registered, documented, and tested. Renderer-sensitive behavior such as repeated page-margin content, physical page counters, automatic TOC target pages, footnotes, sidenotes, bleed, and marks remains gated by the P1–P3 capability model.