Templates, not screenshots
Ten page templates — every one composed from live @protocore/pds components, not a picture of one. They are the shapes every Protocore surface is cut from: marketing, product, the operator console, and the long tail of listing, article, legal, and capture pages in between. Open one to read its structure and lift the composition.
Each template is a real render inside a labelled frame, so what you see is what ships. The prose alongside it names the parts, the order they stack in, and the exact components to reach for — deep-linked to their reference pages.
The front door: a drawn hero, one signal figure, the principles that define the protocol, and a split call to action.
Open patternA single product argued in full — feature split, a tabbed showcase, a proof callout, and a pricing row.
Open patternThe application surface: an app shell with a staging strip, KPI cards, and a server-driven data table with a detail sheet.
Open patternThe first screen a new operator sees — a centered empty state, onboarding steps, and one unmistakable primary action.
Open patternA filterable index of writing: a page header, a chip filter bar, a stack of listing rows, and pagination.
Open patternLong-form reading rhythm — a display title, a byline meta row, pull quotes, code, and a related-reading list.
Open patternThe company page: alternating surface bands, the operating principles, a milestone timeline, and the team grid.
Open patternOpen roles grouped by team with mono labels, the benefits that back them, and a split apply CTA.
Open patternA long-form policy: a sticky table-of-contents rail, numbered clauses, a definitions list, and a last-updated stamp.
Open patternA single-purpose capture card: an inline field-and-button form, a success message, and a privacy note.
Open pattern