Publishing admin rebuild
Replaced a maze of meta boxes with a routed admin SPA. Cut editorial workflow steps by roughly a third.
Senior web developer and architect in Sarasota, Florida. 20 years building things on the web, most of them with WordPress somewhere in the stack.
For a long time "WordPress developer" meant themes and plugins and not much more. That is not the job anymore. The interesting work now lives at the seam between WordPress and the modern JavaScript ecosystem: React running inside Gutenberg, Web Components bridging old themes, admin screens that feel like real software instead of forms from a decade ago.
This site is where I write it down. Patterns that held up in production, things I had to tear out and rebuild, and the occasional lesson I learned the hard way so you do not have to.
Currently: Senior WordPress Developer at Aristotle, building advocacy and political technology platformsBuilding and maintaining WordPress platforms for political advocacy, compliance, and campaign tooling. Custom Gutenberg blocks, REST integrations, and admin workflows that have to hold up under real election-cycle traffic and tight deadlines.
Led front-end architecture across public affairs and advocacy builds. React inside Gutenberg, custom block libraries, democracy-facing platforms, and the glue code that keeps legacy WordPress themes talking to modern JavaScript.
Ran the dev team for an agency focused on nonprofits and mission-driven orgs. WordPress at scale, shared component libraries, client training, and enough project management to keep dozens of sites moving without everything living in one person's head.
PHP, MySQL, custom plugins, and the unglamorous work of making WordPress do things it was not originally built for. This is where I learned how the database layer and hook system actually behave when a client asks for something weird.
Started in retail customer service and moved into management at a Fortune 100 company. Sounds unrelated, but it shaped how I think about users, deadlines, and why your admin UI should not require a training manual.
Replaced a maze of meta boxes with a routed admin SPA. Cut editorial workflow steps by roughly a third.
Shared block package used across three properties. One build pipeline, one design system, zero duplicate React copies.
Dropped modern interactive modules into a theme the client could not afford to rewrite. No jQuery collisions, no framework lock-in.
Where most of my day-to-day work lives.
The JavaScript side of WordPress projects.
Build pipelines, performance, and how the pieces fit together.
The server side when WordPress needs more than posts and pages.
Running projects and teams, not just writing code.
Sectors where I have shipped production work.