# WordPressify

> A Docker-based build system that automates WordPress theme development: one command for the whole environment, a modern asset pipeline behind it, and a distributable theme at the end.

- Disciplines: Web Development
- Live: [wordpressify.co](https://www.wordpressify.co)
- GitHub: https://github.com/luangjokaj/wordpressify
- npm: https://www.npmjs.com/package/wordpressify

![WordPressify](https://hip-spider-874.convex.cloud/api/storage/fc998d0e-25c7-4724-9067-962d1fb23cdc)

## WordPress, without the WordPress workflow

WordPressify is the studio's own build system, open sourced in 2017 and maintained ever since. It exists because theme work had been left behind: the front end had moved on to modules, preprocessors and live reload, while a WordPress theme was still a folder you uploaded and refreshed by hand.

One command brings up the whole environment — database, PHP, web server and asset pipeline — with nothing installed locally but Docker.

- **1** Command to a running stack
- **5** Containers behind it
- **0** Local PHP, MySQL or nginx
- **MIT** Open source since 2017

```bash
npx wordpressify
```
## Two halves of one tool

  
    MariaDB, WordPress on PHP-FPM with Xdebug, a permissions pass, an nginx server, and a Node container running the build. They come up in dependency order and wait on health checks, so the first run ends at a working site rather than a race.
  
  
    Styles compile through PostCSS with imports, mixins and autoprefixing. Scripts pass through Babel and ship as header and footer bundles. Templates, patterns, images and fonts sync into the theme as you save, with live reload in front of all of it.

> Automate your WordPress development workflow.

## From nothing to a theme

  
    `npx wordpressify` writes the project — source tree, theme files and configuration — with no build to wire up afterwards.
  
  
    One command brings the stack up and serves the site with live reload. The watchers poll rather than trust file events, because those do not cross the Docker boundary reliably.
  
  
    A production run minifies everything and writes a distributable theme ready for any host, alongside timestamped backups of a working build.
  

  A project scaffolded on an older version upgrades in place: the installer replaces the build system it owns and leaves the theme source it does not.

## Block themes, first class

The scaffold is a modern block theme — `theme.json`, block templates, template parts and patterns — copied straight into the theme directory as they are edited, so the site editor and the build agree on what a theme is.

The documentation runs on [Doccupine](/work/doccupine), and the tool sits beside the rest of the studio's open-source work: the same argument, applied to whatever the platform happens to be.

---

HTML version: https://riangle.com/work/wordpressify  
Site index for agents: https://riangle.com/llms.txt  
Full content bundle: https://riangle.com/llms-full.txt  
Sitemap: https://riangle.com/sitemap.xml