This page lists the work I deliver as a delivery partner. You pick outcomes. I slot into your team, repo, and release process.
Accessibility
Build accessible UI patterns and fix issues at source. Improve keyboard flow. Reduce support issues.
What I do
- Semantic HTML and predictable interaction patterns
- Keyboard-first UX, focus order, and focus visibility
- Form validation, error messaging, and inline help patterns
- Audit support, triage, and remediation guidance
Deliverables
- Prioritised fix list mapped to templates and components
- PRs with notes for reviewers and QA
- Release QA checklist for your workflow
Performance
Improve Core Web Vitals and page weight. Reduce script and dependency cost. Set budgets and keep them enforced.
What I do
- Core Web Vitals improvements and page weight budgets
- Image, font, and script strategy
- Build output hygiene, dependency reduction, and third-party review
Deliverables
- Before and after metrics pack with the method used
- Performance budget thresholds committed in the repo
- Action list grouped by impact and effort
Static builds
Ship fast, stable sites with a clean build setup. Keep templates maintainable. Add interactivity with progressive enhancement.
What I do
- Astro and Eleventy builds
- Template systems, content models, and collection structures
- Progressive enhancement for interactivity
- Vercel deploy workflows and preview environments
Deliverables
- Clean repo with setup docs and conventions
- Reusable patterns for future builds
- Build checks and basic guardrails for quality
Headless CMS
Set up content so editors move fast without breaking pages. Keep schemas and queries tidy. Support a smooth preview flow.
What I do
- Sanity integration
- Content modelling and schema structure
- Preview setup and editorial workflow support
Deliverables
- Schemas, queries, and templates wired into the build
- Editor guidance notes for fields and page types
- Content rules for consistency across the site
Design system support
Improve consistency and speed across teams. Reduce UI drift. Make components easier to reuse and review.
What I do
- Component standards and governance support
- Tokens setup for spacing, typography, colour, and radius
- Consistent markup and naming for templates and components
Deliverables
- Component inventory notes with gaps and duplicates
- Documentation starter set, usage rules, and examples
- Agreed conventions for PR review and QA
How we work
- Kick-off to agree scope, constraints, and success metrics
- Work in your repo with PRs and clear review notes
- Weekly progress updates with next steps
- Handover with docs and a short backlog of follow-ups