Flow layout

Sidebar

In-flow main/rail composition using CSS Grid as the current side-panel candidate.

Elementef-print-sidebar
CapabilityP0 candidate
Maturityprovisional
Pagination ownerBrowser / selected renderer

Capability note. Grid sidebar fragmentation is intentionally provisional. Current evidence proves bounded marker preservation/separation, not a universal cross-browser paginated guarantee.

Example 1

Evidence rail

Main content stays first in source order and the rail follows it.

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>
  <ef-print-sidebar>
    <main class="folio-sidebar-main">
      <h1>Recommendation</h1>
      <p>Adopt a standards-first print architecture and preserve renderer capability as explicit metadata.</p>
      <p>The main narrative remains the primary source-order content.</p>
    </main>
    <aside class="folio-sidebar-rail">
      <h2>Evidence</h2>
      <p>Chromium 153 experiment.</p>
      <p>Two-page bounded fixture.</p>
    </aside>
  </ef-print-sidebar>
</ef-print-document>
Example 2

Wider decision rail

Rail width is a presentation token, but wider rails increase fragmentation risk and must be tested.

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>
  <ef-print-sidebar style="--ef-print-sidebar-width: 2.1in">
    <section class="folio-sidebar-main">
      <h1>Decision context</h1>
      <p>Applications own content and domain decisions. Folio owns the reusable layout intent.</p>
    </section>
    <aside class="folio-sidebar-rail">
      <h2>Constraints</h2>
      <ul>
        <li>No synthetic pagination.</li>
        <li>Source order must remain logical.</li>
        <li>Fallback must preserve content.</li>
      </ul>
    </aside>
  </ef-print-sidebar>
</ef-print-document>
Example 3

Callout rail

Use side rails for supplementary material, not content whose meaning depends on fixed physical alignment.

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>
  <ef-print-sidebar>
    <article class="folio-sidebar-main">
      <h1>Implementation note</h1>
      <p>Grid is the leading portable side-rail candidate, but the public guarantee remains provisional until deeper geometry and browser evidence exists.</p>
    </article>
    <aside class="folio-sidebar-rail">
      <p class="folio-kicker">Status</p>
      <strong>Provisional</strong>
      <p>Test before relying on multipage alignment.</p>
    </aside>
  </ef-print-sidebar>
</ef-print-document>