This site and Resha

The site is two things. Resha is a theme anyone can use: neutral, token driven, and it works with core blocks alone. Resha Blocks adds the blocks core does not have: a mega menu, a search palette, a reading progress ridge, a table of contents, a video player with chapters. My site is a child theme on top that adds the brand. Everything generic goes to WordPress.org; everything personal stays in the child theme.

Figma is the source of truth. Every colour, space and type size is a Figma variable first, then a theme.json token, and nothing in the code is set by hand. A guard script fails the build on a stray hex colour, a pixel font size or an em dash. The spacing scale is named after its own values, from 2 to 128, so nobody has to remember what “medium” means.

WCAG 2.2 AA from the start: landmarks, a skip link, visible focus, a mega menu that works from the keyboard, real alt text on every image. The editor must look like the front end, so no block renders one thing in the editor and another on the site.

I built this with Claude as a partner across design, code and content. What made it work was rules, not prompts: an owner gate at the end of every phase, verify with screenshots instead of trusting a report, and one layer at a time. What went wrong is part of the story too: an animation bug that only appeared when every drawing shared a page, and a plugin that silently turned animations into stills.

Submitting Resha and Resha Blocks to WordPress.org, then the festival themes that switch the site’s colours for Diwali and Gudi Padwa.