Open-source project
roots/sage avatar
roots/sage

Sage is a Blade-first WordPress theme whose support chat sits behind a sponsorship

WordPress starter theme with Laravel Blade components and templates, Tailwind CSS, and block editor support

13,285 stars2,983 forksPHPMIT

At a glance

What is it?
Sage is Roots' MIT licensed hybrid WordPress starter theme: Laravel Blade and Tailwind CSS for the front end, Vite for builds, and block editor support in the box. The costs live in the details, a Node engine range that leaves Node 21 outside it, translation scripts written for a POSIX shell, and a Discord channel that sponsorship unlocks.
Who is it for?
Sage suits WordPress developers who already work with Blade and want Tailwind and Vite wired up on day one. It does not suit a team that wants a plain PHP theme with no build step, or open community support without paying.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 39 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • roots/sage13,285 ★ · +6
Star history
Repository2026-09-222026-11-15
roots/sage13.3k13.3k

6 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Blade is the source of truth, block support is additive

Sage describes itself as an advanced hybrid WordPress starter theme with Laravel Blade and Tailwind CSS. The hybrid part is the important word: block editor support is listed as built in, and the theme root carries theme.json alongside style.css, functions.php, and index.php, which is the shape of a block-aware theme. The stated benefit is component-based templating through Blade, with the goal of organized code rather than a folder of PHP files.

The consequence for a reader is a decision you have to make per template rather than once. A hybrid theme gives you two ways to render a screen, and the feature list promises both without saying which content types map to which, or what happens when a block template and a Blade view both want the same region of a page. The README does not document that split; it links to installation documentation instead.

The second consequence is about ownership. Once templates are PHP and Blade, the theme is a PHP codebase with a build pipeline attached, and reviewers who expect a drop-in theme folder are looking at the wrong shape of project.

The engine range leaves Node 21 out on purpose

package.json declares engines node as ^20.19.0 || >=22.12.0. That reads as two lanes rather than one floor: the 20 line is capped at the next major, and everything from 22.12 upward is accepted. Node 21 falls in the gap between them, so a machine or a CI image pinned to Node 21 is outside the range the theme declares.

Two other manifest lines matter for what this project is. private is true, so the npm package is never published, and type is module, which means the tooling around it, including vite.config.js, is authored as ES modules.

The build surface is two scripts: dev runs vite, and build runs vite build. There is no test script, no lint script, and no Composer script in this manifest, so the npm side covers asset building only. The consequence is that a team expecting a starter theme with a checked test command will find the verification story lives in PHP tooling and the CI workflow under .github/, not here.

Two Tailwind entries and two Vite plugins share one config file

Five dev dependencies carry the front end. tailwindcss and @tailwindcss/vite are both present at ^4.0.0, which is the split between the engine and its Vite integration rather than a duplicate. Alongside them sit vite at ^8.0.0, laravel-vite-plugin at ^3.0.0, and @roots/vite-plugin at ^2.0.0, so two Vite plugins are installed at once: the Laravel one that Blade-aware builds normally need, and the Roots one that wires the WordPress side.

All of that meets in a single vite.config.js at the repository root. Neither plugin's options, nor the Tailwind entry point, nor the asset output directory appear in the README.

The consequence for a reader is a debugging order. When styles do not appear, or a manifest entry is not picked up, the first files to read are vite.config.js and the two plugin versions, because all three majors here are caret ranges that will float forward on install. A fresh install six months from now resolves newer minors of Tailwind 4 and Vite 8 unless something pins them, which is the opposite of the version stability a WordPress theme on a versioned plugin tree gives you.

Translation scripts assume a POSIX shell and a wp-cli binary

Localization is a chain of six translate scripts in package.json. translate runs translate:pot and then translate:update. translate:pot shells out to wp-cli:

sh
wp i18n make-pot . ./resources/lang/sage.pot --include="theme.json,patterns,app,resources"
wp i18n update-po ./resources/lang/sage.pot $file

translate:update walks every .po file in ./resources/lang and refreshes it from that template. translate:compile then runs translate:mo and translate:js, producing the compiled .mo files and the JSON catalogues, with translate:js passing --pretty-print so the emitted JSON stays readable in version control.

The consequence is that translations depend on two things the theme does not install for you: a wp-cli binary on your PATH, and a shell that understands for file in ...; do ...; done. That loop is POSIX syntax, so npm run translate on Windows needs WSL, Git Bash, or a rewritten script. The --include list is also the definition of where translatable strings may live, and a string placed outside theme.json, patterns, app, or resources will simply never reach the .pot file.

The theme root doubles as the npm project and the theme folder

The top-level listing explains a lot about the layout. There is app/ for PHP application code, resources/ for views, styles, and language files, public/ for what the browser receives, and next to them the WordPress theme files themselves: functions.php, index.php, style.css, theme.json, and screenshot.png. Build configuration sits in the same directory as composer.json, package.json, and vite.config.js.

So one folder is simultaneously a distributable WordPress theme and an npm project with dev dependencies. That is why .gitignore, .editorconfig, .gitattributes, and .github/ matter here as much as any theme file, and why ignoring the wrong path can end up committing build output or ignoring a file the theme needs.

The consequence for a reader is that the directory contract is the first thing to learn and the README does not teach it. The documentation linked from the README, at roots.io/sage/docs/installation/, is where the README sends you to get started, so that page, not this repository description, is what you should read before reorganizing anything.

The support channels split into paid and open halves

The community list has five entries and the first one is conditioned. Joining the Discord is described as sponsoring Roots on GitHub, and the support section says sponsors get access to the private Discord. Open channels follow: Roots Discourse, @rootswp on Twitter, the Roots Blog, and the Roots Newsletter.

The funding model is stated plainly. Roots is an independent open source organization supported only by developers, and sponsorship funds WP Packages and is what keeps the ecosystem independent. Two ways to pay are offered, buying Radicle or sponsoring on GitHub. The listed sponsors are carrot.com, wordpress.com, itineris.co.uk, kinsta.com, ploi.io, and 40q.agency.

The consequence for a reader is a practical one: the fastest route to a human being is a paid one, while Discourse carries the open record. If your evaluation includes how quickly a maintainer answers a question, price that into the decision rather than assuming the chat badge on the front page is open to everyone.

Version 11.2.1 shipped in April and the branch moved in June

The release record is three versions inside two months: v11.1.0 on 2026-03-23, v11.2.0 on 2026-03-25, and v11.2.1 on 2026-04-26. The repository is not archived and its last push is dated 2026-10-07, so work continued on the branch after the last tag.

A major number of 11 says nothing about the toolchain underneath it, and that is the part to watch. The build depends on caret ranges for vite, tailwindcss, @tailwindcss/vite, @roots/vite-plugin, and laravel-vite-plugin, so pinning the Sage version pins the theme's own files and nothing about the tools it builds with.

The consequence for a reader is that a lockfile becomes load-bearing. Two developers on the same Sage tag can end up with different Vite and Tailwind minors, and a build difference between them is a dependency resolution difference rather than a theme bug. Record the lockfile with the project if you want reproducible builds, and re-check the engine range when you move Node versions.

Editorial conclusion

Sage suits WordPress developers who already work with Blade and want Tailwind and Vite wired up on day one. It does not suit a team that wants a plain PHP theme with no build step, or open community support without paying. Before adopting, read the installation documentation at roots.io, check your Node version against the engine range, and decide how translations will run on Windows.

Frequently asked questions

What is Sage from Roots used for?

Sage is an advanced hybrid WordPress starter theme that uses Laravel Blade for component-based templating and Tailwind CSS for styling, with block editor support built in. It is authored by Roots and released under the MIT license.

Which Node versions does Sage support?

The package.json engines field asks for node ^20.19.0 || >=22.12.0, which leaves Node 21 outside the accepted range. The package is marked private and set to type module, so it is not published to a registry.

How do you build the Sage front end?

The dev script runs vite and the build script runs vite build. The dev dependencies are vite ^8.0.0, @roots/vite-plugin ^2.0.0, laravel-vite-plugin ^3.0.0, tailwindcss ^4.0.0, and @tailwindcss/vite ^4.0.0.

How does Sage handle translations?

Npm scripts wrap wp-cli commands. translate:pot generates ./resources/lang/sage.pot with wp i18n make-pot, translate:update refreshes each .po file in that folder, and translate:compile builds the .mo files and the JSON catalogues.

Does Sage support the WordPress block editor?

Yes, block editor support is listed as built in, and the repository ships theme.json at the theme root next to style.css, functions.php, and index.php. Sage is described as a hybrid theme, so Blade templates and block templates both apply.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. roots/sage on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/roots-sage.svg)](https://hysenlabs.com/projects/roots-sage)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/roots-sage.svg)](https://hysenlabs.com/projects/roots-sage)

Was this useful?