Stories about the act of reading and writing itself. — Italo Calvino

Most reading surfaces on the web behave as though the book is a visitor in the browser's house. The browser stays visible — tabs, address bar, chrome, navigation — and the text accommodates itself to whatever space remains. This is not a design decision in most cases. It is simply what happens when you render HTML in a default viewport and do not question the container.

The folio surface inverts that relationship. At narrow viewports, it is a single scrolling column, clean and legible, the way a phone should show a page. But past 1280 pixels, the chrome collapses entirely. The browser recedes. The book fills the screen. Two columns, full-bleed, measured and set. Nothing between the reader and the text but the text itself.

Italo Calvino spent a career writing stories about the act of reading and writing — about readers who become characters, about books that contain other books, about the strange reciprocity between a mind and a page. The folio surface takes that intimacy seriously. It is not a layout. It is an acknowledgment that some texts deserve the full attention of the glass, and that the interface should know when to get out of the way.

The rendering is Pretext-measured and zero-drift, drawn with Canvas2D rather than the browser's layout engine. This is not performance theater. It is a commitment to typographic precision that CSS alone cannot deliver. Every line is placed exactly where the measurement says it belongs. Every glyph sits at its calculated position. The text does not reflow unpredictably because the rendering surface is not the DOM — it is a canvas that knows what the text should look like before it draws a single pixel. The space waits for the words, and the words arrive into the space that was prepared for them.

Navigation is corpus-native. The chapter MDX files live in a chapters/ directory. The reading order is declared in toc.json. The navigation chrome — chapter title, progress indicator, previous and next links — is generated from that structure, not from a content management system or a database query. The book is a directory. The directory is the book. The reader moves through it the way a reader moves through a physical volume: forward, back, returning to the table of contents when lost, never more than one gesture from where they meant to be.

Poetry-aware rendering means that the surface recognizes when it has encountered a poem and adjusts accordingly. Stanzas keep their shape. Line breaks are sacred. The two-column spread respects the integrity of verse in a way that reflowing text never can — because the poem was written to occupy a specific visual space, and the surface was built to honor that space rather than dissolve it into continuous prose.

The spread is not a layout choice among other layout choices. It is the form books were meant to take before screens forced them into narrower shapes. The codex — two facing pages, a gutter between them, the reader's eye moving across the spread as a single visual field — evolved over centuries because it works. The folio surface is not an innovation. It is a restoration.