Document family
Journal and scholarly publication
Standalone scholarly articles and complete multi-article journal issues built from ordinary semantic HTML, existing Folio elements, and generic publication recipes. The consumer owns scholarly content, citations, numbering, identifiers, and editorial decisions; Folio owns reusable publication layout; the renderer owns pages.
New elementsNone
Publication recipes13 in the ef-print-recipes layer
DecisionDF-PRINT-2026-0005
RequirementsFOLIO-JRN-001 to 260
Examples
JOURNAL-ARTICLE-01 · US Letter portrait plus one Letter landscape page
Standalone research article
A fictional two-column research article: opening furniture, kicker, title and subtitle, five authors mapped to four affiliations, ORCID, corresponding author, DOI, dates, licence, structured abstract, keywords, numbered sections, kept and spanning figures, three MathML equations, a code listing, a multi-page table with repeated headers, a boxed limitations callout, declarations, endnotes with backlinks, thirty numeric references in two columns, and a landscape appendix table.
P0 layout · P1 running heads and Page X of Y · P2 deterministic Chromium PDF evidence
JOURNAL-ISSUE-01 · US Letter portrait
Complete journal issue
A fictional 18-page themed issue: cover, masthead with editorial board and publication facts, contents with authored page values, a one-column editorial, three division pages, a research article with author-year references, a review with note-style citations and a spanning table, a brief report with numeric references, a letter, information for authors, a corrigendum, a sponsor page, and a back cover.
P0 composition · P1 per-article running heads and continuous Page X of Y · P2 deterministic Chromium PDF evidence
What each part demonstrates
Renderer capability distinctions
Publication recipes
.ef-longform
Long-form Reading Rhythm
Document-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-backed
.ef-article
Article Unit
A 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-backed
.ef-article-header
Article Front Matter
Opening 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-backed
.ef-authors
Contributor List
Native 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-backed
.ef-affiliations
Affiliation List
Compact 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-backed
.ef-meta-list
Metadata List
Generic 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-backed
.ef-abstract
Abstract
Ruled 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-backed
.ef-caption
Caption
Caption 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-backed
.ef-equation
Display Equation
Display 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-backed
.ef-column-span
Column Span
Full-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-backed
.ef-reference-list
Reference List
Bibliography 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-backed
.ef-endnotes
Endnotes
Authored 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-backed
.ef-declarations
Declaration Group
Back-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-backed
Why recipes instead of journal elements?
A title block is a header, an author list is an ol, metadata is a dl, an equation is a figure around math, a bibliography is a list. Class contracts carry the layout without replacing those semantics, and the same recipes serve reports, proceedings, books, and manuals. Folio adds no ef-print-journal, ef-print-article, or ef-print-citation element. Keywords reuse .ef-labeled and .ef-inline-list; editorial boards reuse .ef-category-grid; the issue contents reuse ef-print-toc.
Authored values versus physical pages
Section, figure, table, equation, and reference numbers, article page ranges, and contents page values are consumer-authored text. Physical page numbers come from the renderer's page counter. JOURNAL-ISSUE-01 records the renderer its contents values were set from, and its tests enforce them only on that renderer.
What remains upstream?
Citation processing (for example CSL), JATS or Markdown conversion, bibliographic validation, DOI registration, peer review, editorial workflow, and mathematics typesetting. See docs/recipes/JOURNAL-PUBLICATION.md for the canonical HTML structure and mapping guidance.