A design that leaves room for the people.
The portfolio’s visual foundation is warm paper, navy ink, editorial serif headings and a plain system-font interface. Real work carries the identity. Motion should help someone locate a change or understand a sequence; it should not hold the content hostage.
A small, reusable language.
Type and readability
Large headings establish hierarchy; body text remains readable and paragraphs stay short. Data uses consistent units, dates and denominators. Exact values stay available in tables.
Buttons, links and focus
Buttons describe an action; links preserve a destination. Hover feedback is also available through visible keyboard focus. Dialogs have a close button, Escape support and a return to the control that opened them.
Motion and responsive layouts
Reduced-motion preferences take priority. No autoplay story or scroll trap is needed. Layouts should adapt to narrow screens and increased text size without hiding essential content.
Content that belongs in WordPress
Posts hold cases and build notes. Pages hold the homepage and reference material. Core blocks organize copy, links, details and collections; dedicated Gutenberg blocks supply the interactive tools. A plugin count is not a measure of WordPress competence.
The decisions behind the decisions.
A small selection of understandable projects and purposeful copy are more useful than a catalogue of effects. The portfolio keeps supporting detail available without requiring every visitor to read it. GitHub portfolio guidance · Webflow’s 2026 design review.
What would change the platform decision?
Evidence from member tasks, editorial effort, accessibility, security, cost and support—not fashion alone. WordPress is a solid foundation today. A future platform should earn its place through a clear improvement for members and the people serving them.