WordPress: base rules for every variant
Theme structure, editable content, enqueue, escaping, Polylang, scripts and the definition of done shared by all WordPress templates.
CMS
WordPress
Six front-end variants for one CMS: expert site, vanilla JS, Alpine, React with the Interactivity API, Vue islands and zero JS. All share the WordPress base rules.
Available to license holders
Log in to the account you used to buy your ContextAdmin license. Downloads and full guides unlock as soon as you are signed in.
WordPress: expert and company site with keyword-targeted content
WordPress expert / consulting site with a custom theme, content driven by a key-based schema (ACF options with code defaults), Tailwind, vanilla JS, Polylang. Revised version (2026-10-15) of an earlier set of guidelines. Shared rules live in the @ files below - copy them to .claude/rules/ in the project.
WordPress: full interactivity in vanilla JavaScript
WordPress, full interactivity in vanilla JavaScript (no libraries). For company and expert sites, blogs and landing pages with a menu, modals, FAQ, a carousel and a form.
WordPress: Alpine.js for light widgets
WordPress + Alpine.js. For themes with many small widgets (filters, calculators, toggles, a header cart), where state kept in HTML reads better than vanilla JS modules.
WordPress: React, Gutenberg blocks and the Interactivity API
WordPress + React. React has two justified places in WordPress: (1) Gutenberg blocks - the editor loads React anyway, (2) the Interactivity API on the front end - declarative data-wp-* directives on PHP-rendered HTML, Preact underneath. Full React on the front end (ReactDOM.createRoot) only for in-page applications: a configurator, a calculator, a customer panel.
WordPress: Vue 3 islands for configurators and calculators
WordPress + Vue 3 as "islands" inside a PHP-rendered page. For calculators, configurators, multi-field filters, bookings. Not for menus, FAQs and modals - those are HTML/CSS or a few lines of vanilla JS.
WordPress: no JavaScript, maximum PageSpeed score
WordPress with no JavaScript on the front end. Goal: 100/100/100/100 in Lighthouse mobile, LCP < 1.5 s on 4G, a page readable by every bot, zero library dependencies. Interactions are done with HTML and CSS. For company and expert sites, landing pages, blogs, documentation. Not for shops with an AJAX cart.