Zum Inhalt springen

How it works

From git clone to a client site that updates itself from GitHub releases.

From clone to live site

  1. Step 1

    Clone and run the setup wizard

    php bin/setup.php sets the theme name and text domain, replaces the PHP namespace, picks the plugins and runs Composer, npm and the first build.

  2. Step 2

    Set the brand

    Colors, fonts and spacing go into config/design-tokens/*.tokens.json. npm run tokens writes them to CSS variables for light and dark mode.

  3. Step 3

    Activate the theme

    On activation the theme creates the basic pages and menus, and it can generate a private styleguide page that renders every module and component with the current tokens.

  4. Step 4

    Build the pages

    Editors compose pages from the modules. Logo, contact data, footer and analytics live in the theme options.

  5. Step 5

    Ship updates

    Conventional commits drive semantic release. Each GitHub release carries the theme zip and its checksum, and sites pick it up in the WordPress dashboard.

Stack

Stack
Part Technology
Templates Laravel Blade (Illuminate v13) with components such as x-section and x-button
Styles Tailwind CSS v4.1 on top of generated design tokens
Scripts TypeScript and Alpine.js, bundled with Vite 8
Content model Classic Editor, ACF Pro Flexible Content, ACF Extended
PHP 8.3 or newer, strict types, service providers
Plugins Managed with Composer through wpackagist.org

Under the hood

Service providers

The theme boots a list of small providers, each with one job: Blade, ACF, security headers, SEO, images, menus, updates, logging. A feature is easy to find and easy to switch off.

Fields in PHP

All ACF fields are defined in PHP, not in the database or JSON. They live in version control and one definition serves every module that needs it.

Want a site built on it?

I design and build websites, apps and AI tools in Fürth, Germany. If you need a WordPress site your editors can maintain without breaking it, get in touch.
Visit rafaelalex.de