01
Block themes done right
theme.json as the single source of truth. Templates and template parts in the right places. Patterns registered properly. Style variations for the brand variants you need.
Site Editor works the way Gutenberg intends.
Service Themes
Block themes, hybrid themes, classic themes. Built to your design, fast by default, accessible by default, ready for WooCommerce and BuddyPress without override wars.
Why custom themes
Page builders bloat the page weight. Premium themes lock you into their patterns. Override CSS fights the original styles. By the time the brand is right and the performance is acceptable, the team has spent more on customization than a proper theme would have cost in the first place.
We build themes from your design tokens, your component library, and your real content. The theme matches the brand on day one, the page weight stays in budget, and editors can extend it through the Site Editor without code changes.
What we build
Block-first, hybrid where it makes sense, classic when WooCommerce and BuddyPress need it. Pixel-parity with your design. Fast, accessible, plugin compatible.
01
theme.json as the single source of truth. Templates and template parts in the right places. Patterns registered properly. Style variations for the brand variants you need.
Site Editor works the way Gutenberg intends.
02
Not every site is ready for full block themes. We build hybrid themes (block templates + classic PHP for the parts that need it) and pure classic themes when WooCommerce, BuddyPress, or LearnDash require it.
Theme architecture matches the product reality.
03
Figma to WordPress with no degradation. Type scale, spacing scale, color tokens, every component. We design in tokens and build in tokens, so light and dark variants ship from the same source.
Brand stays consistent across every page.
04
No render-blocking JavaScript. Critical CSS inlined. Web fonts subsetted and preloaded. Lazy loaded images with proper dimensions. Core Web Vitals pass on launch day.
PageSpeed scores stay above 90.
05
Color contrast ratios verified. Focus states visible on every interactive element. Keyboard navigation works for the entire site. Screen reader labels on every icon-only button.
Accessibility audit passes.
06
Themes shipped tested against the major plugin ecosystems. Cart pages, account pages, member profiles, course pages all match the brand without overrides fighting the plugin styles.
Plugins look native, not bolted on.
30,000+
active sites running BuddyX, our community theme
Built by the same team. WordPress.org rated 4.7 stars.
theme.json
Every block theme we ship uses theme.json as the design token source. Colors, fonts, spacing, fluid type scale. The Site Editor picks them up automatically. CSS overrides become the exception, not the rule.
{
"$schema": "https://schemas.wp.org/trunk/theme.json",
"version": 3,
"settings": {
"appearanceTools": true,
"color": {
"palette": [
{ "slug": "brand", "color": "#1C55E9", "name": "Brand" },
{ "slug": "accent", "color": "#FFAD0D", "name": "Accent" }
]
},
"typography": {
"fontFamilies": [
{
"slug": "inter",
"name": "Inter",
"fontFamily": "'Inter', system-ui, sans-serif"
}
],
"fluid": true,
"fontSizes": [
{ "slug": "small", "size": "0.875rem", "fluid": false },
{ "slug": "medium", "size": "1rem", "fluid": false },
{ "slug": "large", "size": "clamp(1.25rem, 2vw, 1.5rem)" }
]
},
"spacing": {
"spacingScale": { "steps": 8 }
}
},
"styles": {
"color": { "background": "#fff", "text": "#111827" },
"typography": { "fontFamily": "var(--wp--preset--font-family--inter)" }
}
}
Process
01
One week. Design audit, token extraction (color, type, spacing), component inventory, page templates needed. Output is theme.json plus a component build plan.
Build starts with the design system locked.
02
Four to ten weeks depending on scope. Components built one at a time, reviewed in the browser at every breakpoint, signed off before the next one starts.
No surprises at the final review.
03
One to two weeks. Cross-browser testing, accessibility audit, performance audit, plugin compatibility check. Documented handover.
Launch with passing audits.
Common questions
Block theme if the site is content-driven and editors will use the Site Editor. Classic theme if the site is heavily integrated with WooCommerce, BuddyPress, or LearnDash where Full Site Editing is still maturing. Hybrid when you want both. We pick the right architecture in discovery.
Both. We have customized BuddyX, Astra, Kadence, Blocksy, GeneratePress, and many others. We also build from scratch when the brand needs full control. The choice depends on budget, timeline, and how much of the existing theme you actually use.
Yes for block themes and hybrid themes. theme.json drives global styles, templates and patterns are registered, style variations cover your brand variants. Editors can change colors, fonts, and layouts without touching code.
Yes through our retainer. We push WordPress core compatibility, plugin compatibility, and design refinements. Themes ship with a child theme pattern from day one so your overrides survive updates.
Yes. We build to design tokens (colors, type scale, spacing scale) extracted from your Figma file. Components get built one at a time and reviewed against the design before the next one starts. No "close enough" approach.
Theme customization (existing theme, brand alignment) are scoped per project. Custom theme builds from scratch are scoped after discovery depending on page count and complexity. Discovery call is free, fixed-price quote within 48 hours.
Need a theme that fits the brand?
Discovery call is free. Fixed-price quote within 48 hours. Projects are scope-dependent.
After 16 years of buying WordPress themes and plugins, I know exactly what bad support looks like and Wbcom Designs is the polar opposite. My setup was a nightmare: multiple tools, deep integrations, custom configurations that required…