Case study
A professional portfolio with a clearer public-service story
This site brings together my Arizona political work, ASU education, earlier professional experience, and selected projects in a format that is direct, accessible, and easy to maintain.
- Role
- Content direction, visual direction, and review
- Timeline
- July 2026
- Platform
- Next.js and Netlify
The goal
Present the work without overstating it.
Present a credible early-career story without inflating experience, exposing private information, or making the site resemble an active campaign.
The constraints
Boundaries shaped every choice.
- Political and public-service work must lead.
- Public claims must remain conservative and source-controlled.
- Private campaign and personal information must remain unpublished.
- The site must stay lightweight, accessible, and maintainable.
The decisions
Evidence and hierarchy before decoration.
- Start with identity and current role.
- Replace repeated claims with specific evidence.
- Use a restrained Arizona civic-editorial visual system.
- Add a precise civic-tech layer without generic technology aesthetics.
- Keep digital projects secondary.
The implementation
A small, maintainable Next.js site.
The site uses Next.js 16, React 19, TypeScript, custom CSS, and self-hosted Newsreader and Public Sans fonts. Pages use Server Components by default. Client-side JavaScript is limited to the accessible mobile menu and résumé print button.
A code-built Arizona signal field, responsive editorial grids, and route-specific compositions create the visual system without an animation or component library. Centralized metadata helpers control canonical URLs, social cards, and index rules, while small JSON-LD blocks describe the site, public profile, and visible breadcrumbs.
I directed the content, visual decisions, and final review. AI-assisted development tools supported implementation, testing, and revision.
The verification
Review the story and the system together.
Verification for this revision covers responsive behavior, keyboard access, accessibility structure, content guardrails, links, metadata, security headers, and the production build.
- Responsive reflow and horizontal-overflow checks from 320-pixel phones through large desktops
- Keyboard access, visible focus, mobile-menu Escape handling, and focus return
- Automated WCAG accessibility scans for all four public routes, with manual review of contrast and native-dialog behavior
- Rendered content guardrails for privacy, prohibited claims, links, and public facts
- Route-specific metadata, canonical URLs, social cards, JSON-LD, robots, sitemap, and 404 behavior
- A rendered US Letter print proof for the public HTML résumé
- Lint, strict TypeScript, dependency audit, production build, and production-rendered route tests
The result
A public-service story with room to grow.
A clearer, more credible professional story that can grow with new education, experience, and public-service work without losing factual discipline.