Nathan Wrigley’s Jukebox Podcast on WP Tavern features Rob Ruiz, a designer-turned-developer who now works as an architect at an agency and maintains WP Rig — an opinionated, open-source starter and toolkit for building WordPress themes. WP Rig is a minimal, modern scaffold that combines Composer and Node tooling, enforces WordPress coding standards, and lets teams use contemporary CSS features today.

How Rob became involved
Rob started using WordPress around 2010. After trying several frameworks he landed on WP Rig for its pragmatic opinions and alignment with WordPress Core. When the original maintainers needed new caretakers, Rob joined a maintainer meeting and gradually became the primary steward, taking responsibility for updates and occasional contributors.

What WP Rig is
WP Rig functions as both a starter theme and a developer toolkit. Think of it like a modern, opinionated underscores: a clean base that includes Node and Composer dependencies plus developer tools to automate common tasks. It handles CSS processing, linting, bundling, and other build steps while avoiding unfamiliar templating systems. The goal is to stay lean and familiar so developers can customize without fighting the framework.

Who benefits from WP Rig
WP Rig is useful for several types of users:
– Designers and front-end developers who want modern CSS workflows and better control over styles.
– Agency teams that need consistent patterns, shared tooling, and enforceable coding standards across projects.
– Developers who want to move beyond page-builder constraints and learn how themes are built, growing into full-stack theme work.

Why people like it
Rob highlights WP Rig’s minimalism and strong CSS tooling. The setup makes it easy to use modern CSS features (for example, nesting) through PostCSS or other processors before full browser support arrives. It doesn’t force a new templating paradigm, so WordPress developers can keep familiar theme architecture. For teams, the shared conventions and automated checks simplify reviews, handovers, and client delivery.

Learning curve and approach
Using WP Rig nudges you toward code-based site control. It’s well suited for anyone ready to step beyond the admin UI and page builders into HTML, CSS, JS, and PHP. There is a learning curve: you’ll work locally and learn some build tooling, but the project is designed so you can tackle one area at a time — for example, start by focusing only on CSS — and progress incrementally.

Tooling and prerequisites
WP Rig runs locally and depends on:
– Node.js for JavaScript tooling
– Composer for PHP package management
– A local WordPress environment (Local, Docker, wp-env, etc.)

Development tasks like CSS compilation, JavaScript bundling, TypeScript builds, linting, and tests happen on your machine. When you’re ready to ship, WP Rig provides a bundling step that prepares a final theme package, replacing WP Rig references with your theme name so the distributed theme looks like your own work.

Themes, blocks, and Full Site Editing
Full Site Editing and block-based themes have shifted how themes are built. WP Rig began in the classic theming paradigm but can be adapted to block themes or hybrid (universal) approaches. The toolkit includes commands to adjust the scaffold for FSE and supports block authoring at the theme level.

There’s an ongoing debate about whether blocks belong in plugins or themes. Theme-level blocks make sense when a block is tightly coupled to a theme’s design or navigation, but bundling blocks into a theme can make that theme ineligible for the wordpress.org directory. WP Rig doesn’t force a stance; it gives developers the tools to author blocks in whichever paradigm they choose and to weigh those trade-offs.

Education and guardrails
A major aim of WP Rig is teaching good, safe practices. The project includes documentation, video tutorials, and built-in checks to help developers follow WordPress best practices. Tools like PHPCS with the WordPress Coding Standards are integrated so themes can be validated before submission, reducing friction when preparing themes for clients or contributing to the wordpress.org repository.

The emphasis is on guardrails: automated checks that surface issues early while guiding developers to understand the reasoning behind best practices. That makes the learning curve less error-prone and more instructive.

Community and maintenance
When Rob took over, much of the early community had drifted away. Maintaining a modern toolkit demands not only WordPress knowledge but familiarity with contemporary front-end tooling (esbuild, Lightning CSS, Vite-era patterns). Today the project is largely driven by Rob with occasional contributors. WP Rig maintains a Discord server, a YouTube channel, and a GitHub repo with contribution guides and issue tracking. Rob hopes the launch of version 3 — a significant overhaul focused on speed and modern tooling — will attract more contributors.

Why WP Rig matters
Rob stresses that WordPress’s future depends on contributors and tinkerers. Tools that lower the barrier to learning and producing standards-compliant themes help sustain the ecosystem. WP Rig aims to make it easier for developers to build robust themes, learn best practices, and eventually contribute back to WordPress Core.

How to get started
Explore WP Rig at wprig.io for Learn documentation, contribution instructions, and links to Discord and YouTube tutorials. Rob is active on LinkedIn and the WP Rig Discord and is available to answer questions or help new users get started.

Summary
WP Rig is a modern, minimal starter theme and developer toolkit focused on developer experience, modern CSS, code quality, and education. It supports classic, hybrid, and block paradigms, integrates build and linting tools, and provides guardrails that help developers write better WordPress themes. Visit wprig.io or the GitHub repo to try it, follow the tutorials, and contribute.

WP Rig is a lightweight, opinionated starter toolkit for building WordPress themes that blends modern front-end tooling with WordPress best practices. It provides a structured starting point without imposing unfamiliar templating paradigms, and it includes build and linting tools so teams can write forward-looking CSS and JavaScript while staying aligned with WordPress standards.

What WP Rig provides
– A minimal starter theme and developer toolkit that integrates Composer and Node-based build tools. It automates common tasks like compiling CSS, bundling JavaScript, and running code standards checks so you can focus on theme design and functionality.
– Support for modern CSS workflows: you can write future-friendly CSS features today (for example, nesting) and have them compiled for current browsers using fast tooling such as esbuild or Lightning CSS.
– Linting and standards enforcement for PHP, JS, and CSS, including the WordPress PHP Coding Standards via PHPCS, helping teams catch issues early and maintain consistent quality.

Rob Ruiz and the project
Rob, originally a designer who moved into development, discovered WP Rig while evaluating theme frameworks and liked its small, WordPress-focused approach. After connecting with the prior maintainer, Rob took over stewardship of the project and led a major modernization (WP Rig v3), replacing older build tooling with faster alternatives and refining the workflow with contributors.

Who benefit from WP Rig
– Developers building custom, production-ready themes who want modern workflows and repeatable scaffolding.
– Designers and hobbyists learning how themes are constructed and gradually stepping into development.
– Agencies and teams that need shared opinions and guardrails to keep multiple projects consistent and maintainable.

Why teams choose it
– Minimal core: provides scaffolding and sensible defaults without adding foreign conventions that separate the theme from the WordPress ecosystem.
– Team alignment: built-in checks and automation reduce inconsistent practices, improve code quality, and make onboarding easier.
– Forward-looking tooling: modern CSS/JS pipelines let teams use recent language features while producing production-ready assets.

How you use it and the learning curve
WP Rig assumes local development on your machine rather than editing directly in the WP admin. That makes the toolkit approachable: you can start small by only touching CSS, or expand into full custom functionality as you learn. The project is meant to be educational and gradual — it helps people tinker in a safe environment and adopt correct practices over time. Rob emphasizes that coding provides precise, global control over site output, even though page builders can be useful for quick starts.

Requirements and workflow
To use WP Rig you typically need a local WordPress development environment (LocalWP, Docker-based setups, wp-env, etc.), Node.js for JS build tooling, and Composer for PHP dependencies. Development happens locally; the toolkit builds a distributable theme bundle, replacing WP Rig references with your theme name so the output is a clean, standalone theme ready for deployment or distribution.

Full Site Editing and blocks
WP Rig began in the classic theme space but now supports classic, hybrid/universal, and block-based themes. The toolkit includes commands to convert a starter into a block or hybrid theme. While Full Site Editing moves some design work into the admin UI and can reduce the need for hand-coded templates, there are times when theme-level blocks are appropriate (for example, bespoke navigation). A caution: bundling blocks into a theme can affect eligibility for the wordpress.org theme repository, so consider distribution plans before baking blocks into a shipped theme.

Education, guardrails, and documentation
A big part of WP Rig is learning: the project includes documentation, video tutorials, and examples to help developers understand modern front-end tooling within a WordPress context. Automated checks and linting help catch issues before you try to publish or share a theme, reducing rework and helping contributors learn good practices.

Project health and community
Since taking over maintenance, Rob rebuilt key parts of WP Rig to modernize performance and the developer experience. The contributor base has shrunk compared to the original launch, so maintenance currently relies on Rob plus occasional contributors. There is an official Discord server and a YouTube channel linked from the site, and the code and contribution guides are on GitHub. Rob invites more contributors to try v3, report issues, and help grow the project.

Why contribute or adopt WP Rig
Using or contributing to WP Rig helps you learn modern theme development while supporting an open-source tool that promotes WordPress best practices. It supports multiple theme paradigms, enforces standards, and is free to use. Whether you want a consistent toolkit for team projects or a learning platform to move from designer to developer, WP Rig is designed to make that transition smoother.

Where to find WP Rig and contact Rob
Project site and docs: wprig.io. The site links to Discord, YouTube, and GitHub. Rob is reachable via the Discord community listed on the site and on LinkedIn.

This episode of the Jukebox Podcast is a useful listen for anyone interested in theme development, modern WordPress tooling, or contributing to a focused, open-source starter theme and toolkit.