Contact page
A page head, a two-column form with expectations in the rail, the link cluster, and a native-details FAQ accordion.
Native inputs, native validation — nothing here reinvents either.
The form
Three fields, one button, the same .field every form on the site uses.
.field · .label · .input
Or find me elsewhere
Icon buttons, not a social bar bolted on separately.
The page head, not a hero
.page-head — a hero states, a page head just labels. Contact is not making a case, so it gets the quiet band. Defined in 30-header.css; nothing used it before these pages.
Say hello
For work, a correction, or just to say a lesson helped.
.page-head · .page-head-sm
What to expect, in the rail
A form with no stated response time is how "did that even send?" happens — so the two-column layout puts expectations beside the form rather than after it.
.col-widget + .stats-bare — the rail widget every collection post uses
The FAQ accordion
Native <details>, so the keyboard and find-in-page work for free. .acc wraps a stack of .collapse — both defined in 28-disclosure.css and unused by any page until now.
Do you take freelance work?
Can I use this commercially?
Will you review my CSS?
.acc · .collapse · .collapse__body — no JavaScript involved