What changes when I switch from `layout: one` to `layout: two`?

`layout: two` activates the `grid-two` template, adding a right-hand sidebar that collapses beneath the main column on smaller screens.

How do I tailor the sidebar for a specific page?

Edit `views/partials/sidebar.php` or inject a custom partial via `slot_after_main` to swap resources per route.

A two-column tour of how the new parchment UI, slots, and front matter work together.

About this demo

This page mirrors the production two-column layout: generous main content on the left, contextual resources on the right, both styled with the refreshed Markdown skin.

Anatomy of the two-column layout

Main column for long-form stories, walkthroughs, or release notes.
Sidebar for quick links, callouts, and microcopy that should stay visible.
Responsive stacking that drops the sidebar below the content on small screens.

How the design language shows up here

Headlines use the display font from redesign/styles.css, while body copy matches the GitHub Markdown palette.
Blockquotes, definition lists, and code fences inherit the parchment gradient from markdown-github.css.
Inline links pick up the ink-colored underline when hovered, matching the banner and footer accents.

Editorial patterns we recommend

Keep paragraphs short—let the textured canvas breathe.
Group related links into unordered lists to benefit from the soft list bullets.
Use the qa-block pattern (shown below) for quick-hit Q&A content.

Quick answers

Can I adjust column widths?: Yes. Tweak the CSS grid values in public/css/app.css or override them per page with a small inline style block.
Where do sidebar links live?: By default they come from views/partials/sidebar.php, but you can inject a custom partial via slot_after_main.
How does the markdown skin affect tables?: Tables inherit the parchment panel, zebra stripes, and scroll affordance that you see in markdown-demo.html.