brand
Hiring managers, engineering leaders, product-minded engineers, and peers reviewing Steve P's work, writing, and current toolchain. They arrive from search, GitHub, social previews, or shared links and need a quick sense of taste, technical judgment, and credibility.
This portfolio presents Steve P as a Cambridge-based senior frontend engineer and AI product builder. Success means visitors understand the work, trust the engineering craft, and can move naturally into projects, writing, or contact paths.
Technical, precise, energetic. The tone should feel current and hands-on without drifting into generic developer-site theatre.
Avoid bland SaaS landing-page templates, generic AI-workflow dashboards, beige editorial restraint, and decorative tech visuals that do not connect to the actual portfolio.
- Show the real surface: previews and supporting visuals should reflect the portfolio people are visiting.
- Keep the engineering signal clear: every section should make the stack, workflow, or output easier to understand.
- Use neon energy with discipline: the palette can glow, but hierarchy and readability come first.
- Make navigation obvious: every page should offer a direct next step into projects, writing, or home.
- Respect motion preferences: animation should add polish without hiding content or blocking reduced-motion users.
Target WCAG AA contrast for core text and controls. Maintain keyboard access, visible focus states, reduced-motion fallbacks, and readable layouts from mobile through desktop.