roots/sage
This system is a modernized WordPress theme built on the Sage 10 architecture, integrating Laravel's Acorn framework and Blade templating engine. It manages frontend assets through a Vite build pipeline and utilizes Tailwind CSS for styling, replacing older PHP-based template hierarchies and jQuery plugins with a modular, component-driven structure. The theme handles standard WordPress template rendering, form generation, and asset compilation while enforcing strict PHP and Node.js version requirements.
48.6
Weak · 2 August 2026
620
lines of production code
PHP
with JavaScript
2
bus factor · 264 authors in all
3
measurements over time
How it got here
2011 · Modernization and architecture overhaul
The project underwent a major architectural shift, replacing the previous PHP-based templating system with Laravel Blade and integrating the Acorn framework. This period also involved stripping out legacy CSS frameworks and bundled JavaScript libraries in favor of modern build tools and standardized structures.
6 changes
2012–2017 · Vite and Blade migration
This period focused on modernizing the project's build pipeline by migrating from Webpack to Vite and upgrading to Tailwind CSS 4. The codebase was refactored to use Laravel Blade templates for all views, consolidating theme initialization and standardizing the rendering of content and layouts.
5 changes
2020–2025 · Sage 10 migration and Tailwind CSS upgrade
This period focused on modernizing the project's architecture by migrating to Sage 10, which involved restructuring service providers and view composers. The team also upgraded to Tailwind CSS v4 and introduced new UI components and JavaScript entry points to support the updated theme structure.
9 changes
Survey your own repository
roots/sage was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 2 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 56249ebd49 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.