Block Theme Development
I build governed block themes: theme.json design rules, Site Editor templates, and pattern libraries that let editors publish without breaking anything. You get a documented system another developer can maintain, not a homepage hiding a mystery layer.
WordPress Core contributor, building on the block editor since it shipped
Replies within 24 hours, usually the same day
Work delivered for, or alongside, teams at:
What it costs
The base price covers a complete governed theme. Migration volume, WooCommerce, and custom blocks add scoped line items you approve before work starts.
WooCommerce templates and custom blocks are scoped as add-ons.
All prices include GST.
How this runs
I review your templates, content, plugins, and editor pain points, plus the migration risk if you’re leaving a builder. The build map comes from what your team publishes, not from a theme demo.
You leave with: a build map covering tokens, templates, and patterns.
I build the hardest template or migration path first, before multiplying the design across the site. If something is going to fail, it fails cheap and early.
You leave with: the riskiest piece proven on staging.
The theme, patterns, block styles, and any focused custom blocks come together on staging. Native blocks first, custom code only where the content model demands it.
You leave with: a complete governed theme you can click through.
Content migrates through responsive, accessibility, and performance checks. Then your team gets source files, launch notes, known limits, and a walkthrough built on their real tasks.
You leave with: a system another developer could maintain tomorrow.
I start with the editors, not the homepage. A block theme succeeds when the people publishing every week can do their jobs without inventing new spacing or colors, so I model the patterns around their actual tasks.
I put every design decision in theme.json where it can be governed, instead of scattering CSS overrides nobody will find later. One source of truth, and the Site Editor respects it.
What I refuse to build is a locked black box. You get source files, documentation, and a handoff any capable WordPress developer can pick up.
— Gaurav
Before you write in
Not answered here? Ask directly and you will hear back within 24 hours.
Builds start at ₹75,000, including GST. The final quote depends on your templates, content volume, integrations, and migration risk, and you get a fixed scope with deliverables and exclusions before work starts.
Yes, but I audit the content before promising a clean migration. Standard posts and pages map to native blocks. Custom builder widgets each need an equivalent pattern, block, or template, and I plan that replacement work on staging so the live site stays intact.
That’s the whole point. Editors get controlled patterns, sensible choices, and templates matching the jobs they actually do. They publish quickly without inventing spacing, colors, or layout rules on every page.
Yes. The Figma system becomes theme.json tokens, templates, patterns, and block styles. I’ll also flag designs that will create editing or responsive problems before they turn into expensive code.
Not always, and I’ll tell you when it isn’t. If your builder site is stable and cheap to run, keep it. The case for switching is real when performance, lock-in, or editing friction costs more per year than the rebuild costs once.
About me
A WordPress Core contributor with plugins running on more than 10,000 sites.
Development clients get the person who ships his own plugins, not a project manager.
I was a teacher before I was a developer. I taught mathematics to competitive-exam students, which is why I explain hard things plainly instead of hiding behind jargon.
What I am actually good at is the join: technical SEO, fast front-ends, and content treated as one system instead of three vendors blaming each other.
Describe your site, your team, and the edits that turn into tickets. I’ll reply with the smallest useful rebuild and what it would cost.
Replies within 24 hours, usually the same day
