r/WordPressThemes • u/Living-Pen-3905 • 4h ago
Anyone else building client sites with a single "structural-only" parent theme and ultra-thin CSS "Skins"?
Hey everyone,
Solo designer and dev from Japan here (using AI to help with my English!).
Over the years of maintaining and rescuing messy client WordPress sites, I got tired of dealing with stacked CSS overrides, \`!important\` wars, and layouts breaking every time a theme updates.
So I settled on a very strict architectural rule for all my client builds:
\- \*\*1 Shared Parent Theme (Structure & Safety Only):\*\* Handles semantic HTML, update resilience, security, and baseline accessibility (skip links, keyboard focus, No-JS fallbacks). It has almost zero visual opinion and is \*never\* modified per client.
\- \*\*Ultra-Thin Child Themes ("Skins"):\*\* Each client gets a lightweight child theme strictly limited to visual layout and styling. No core template overrides, no bloated PHP, and clear boundaries between theme and plugins.
It makes multi-year maintenance and full redesigns dramatically cleaner—you just swap or rebuild the Skin without touching the underlying WordPress foundation.
For those running small studios or solo shops: do you use a similar "structural parent + visual skin" split, or have you moved completely to block themes / FSE / custom starter themes per project? Would love to hear how you approach long-term maintainability!