Anatoliy Dovgun

Methodologies · Frontend Methodologies Component-Driven Development Build and document UI in isolation — Storybook-style workflows for blocks. Component-driven development for WordPress blocks and editor UI This guide is…

Methodologies · Code Design & Testing BDD Given-When-Then behavior specs; Behat and Codeception for WordPress acceptance tests. Behavior-driven development and acceptance testing in WordPress projects This guide is…

Methodologies · WordPress Methodologies Block-first / Gutenberg-first Ship features as blocks and block.json instead of classic PHP templates. Block-first and Gutenberg-first methodology for WordPress product development This guide…

Methodologies · WordPress Methodologies Headless / Decoupled WordPress WordPress as backend via REST or WPGraphQL; React or Next.js frontends. Headless and decoupled WordPress architecture methodology and practices This…

Methodologies · WordPress Methodologies API-first / REST-first Design endpoints and contracts first; UI and blocks consume REST second. API-first and REST-first design methodology for WordPress products This guide…

Methodologies · WordPress Methodologies Full Site Editing / theme.json Block themes driven by theme.json, patterns, and template parts. Full Site Editing and theme.json methodology for WordPress block themes…

Methodologies · Frontend Methodologies Atomic Design Atoms → molecules → organisms — maps to blocks, patterns, and templates in FSE. Atomic Design methodology for WordPress blocks, patterns, and…

Methodologies · Frontend Methodologies BEM Block-Element-Modifier naming for predictable CSS in themes and blocks. BEM naming methodology for WordPress theme and block CSS architecture This guide is a…

Methodologies · Frontend Methodologies OOCSS / SMACSS Alternative CSS organization for large themes and design systems. OOCSS and SMACSS CSS organization for large WordPress frontends This guide is…

FSE Multilingual 4WP Multilingual FSE Locale-aware FSE template parts for Polylang and WPML — keep header and footer in your templates, swap language-specific parts on the front end.…