Available — 25–30 hrs / week
I'm Rhys — a front-end developer in the Midlands. I take build work off studios who've won more than they can staff: Next.js front ends, headless CMS integrations, and applications that hold up under real use.
Booking platform
A booking system for a three-practitioner clinic: a multi-step flow with URL-addressable state, a real availability engine, and a staff-side week grid. Built to show stateful application logic rather than marketing pages.
All nine routes render with Postgres stopped
Editorial site + headless CMS
A magazine site on Sanity: a content model an editor can use without a manual, side-by-side preview that renders an unpublished draft on the real site, and tag-based revalidation driven by a publish webhook rather than a timer.
Lighthouse 97 / 100 / 100 / 100 / 100, mobile
Analytics dashboard
A dense SaaS dashboard over 4,000 seeded customers: server-side filtering and paging, cohort grid, and charts that stay readable at 360px and in greyscale. Tested by listening to it with a screen reader, with the transcripts in the repo.
20 NVDA scenes, transcripts checked into the repo
These are my own builds, made to show how I work — not client projects, and not written for a brief anyone paid for. Every number on this site is measured against the deployed build, and the method is in each repo.
Every number on this site was run against the deployed build after the last commit. Lighthouse figures are the lowest of five runs, not the median. Where a score went up between measurements without a change that could explain it, the README says so instead of banking it.
A green check that cannot go red is worse than no check. Every probe in these builds was run against a page carrying the defect it looks for. One audit found four of a sweep's own checks quietly passing — including a sideways-scroll test behind which both chart axes had been invisible at 360px for months.
Each build has decisions in it that cost something: a slower request after publish, ten SEO points on one route, no loading skeleton. They are in the READMEs with the price attached. A studio inherits those trades, so it should be able to read them before it inherits them.
Next.js front ends on Sanity, Storyblok or Contentful. Structured content models editors understand without a manual, preview that actually previews, and pages that stay fast after the client adds four hero videos.
Auth, dashboards, booking flows, multi-step forms, integrations. Server components where they help, client state where it is needed, and tests around the parts that would embarrass us both.
Core Web Vitals as a delivery requirement rather than a nice-to-have, and WCAG 2.2 AA as the baseline. If you sell accessibility to your clients, I will not be the reason the audit fails.