Skip to content
CAI
Software that uses CAICheck a score

roots/sage

47.4

Weak · 13 November 2026

620

lines of production code

PHP

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a WordPress theme that has been completely rewritten using the Sage 11 architecture, leveraging Laravel, Blade templating, and Vite for asset management. It replaces legacy CSS frameworks and jQuery plugins with Tailwind CSS v4 and modern JavaScript entry points to handle site layout, content rendering, and block editor integration. The theme provides modular components for navigation, search, alerts, and post content, while maintaining core WordPress functionality through Acorn service providers and view composers.

How it got here

2011 — Sage 11 modernization rewrite

6 changes.

This period involved a complete architectural rewrite of the theme into Sage 11, migrating the stack to Laravel, Blade, Vite, and Tailwind CSS. Legacy assets, including custom stylesheets, the Blueprint CSS framework, bundled jQuery plugins, and CodeMirror, were removed to align with the new modern development workflow and dependencies.

2012–2017 — Sage 10 migration and modernization

5 changes.

The project migrated to the Sage 10 theme architecture, replacing legacy templates with a new set of Blade views and partials for improved maintainability and semantic structure. This update integrated Vite 8 and Tailwind CSS 4 into the build system, requiring newer PHP and Node.js versions, while enhancing accessibility and WordPress core feature support.

2020–2025 — Sage 10 and Vite migration

9 changes.

The project underwent a significant architectural shift to integrate Sage 10 and Acorn v3, replacing the legacy Laravel service provider structure with a dedicated ThemeServiceProvider. This period focused on modernizing the build pipeline by adopting Vite for JavaScript and upgrading to Tailwind CSS v4, while refactoring view logic into modular Composer classes and section components to improve maintainability.

Features

Add Alert component with Tailwind CSS styling

A new Blade component for alerts has been added to the application. It accepts a 'type' prop (success, caution, warning, or default) to determine the color scheme using Tailwind CSS utility classes and renders the provided message or slot content within a styled div.

resources/views/components · high confidence

Add search form component with accessible markup

A new search form view has been added at resources/views/forms/search.blade.php. It renders a standard HTML5 search form that submits via GET to the home URL, featuring a screen-reader-only label, a search input pre-filled with the current query, and a submit button. This provides the underlying template structure for the site's search functionality.

resources/views/forms · high confidence

Added placeholder directories for fonts and images

Created empty \resources/fonts\ and \resources/images\ directories (via \.gitkeep\ files) to serve as standard locations for storing font and image assets within the project structure.

resources/fonts, resources/images · high confidence

Sage 11: Complete rewrite with Laravel Blade, Vite, and Tailwind CSS

The theme has been completely rewritten as Sage 11, replacing the legacy Roots architecture with a modern Laravel-based stack. The templating system now uses Laravel Blade (evidenced by the new \index.php\ using \view()\ and the \vite.config.js\ configuration) instead of standard PHP templates. The build workflow has shifted from Grunt/Bower to Vite, with \vite.config.js\ defining the new asset pipeline and \theme.json\ providing block editor configuration. The legacy template files (such as \header.php\, \footer.php\, \loop.php\, and various page templates) have been removed, and \functions.php\ now initializes the Acorn application container. The theme now requires PHP 8.3 and WordPress 6.6+, and the default styling framework is Tailwind CSS.

(repo-wide) · high confidence

Removals

Removal of Blueprint CSS framework files

The Blueprint CSS framework files (including screen.css, ie.css, print.css, and the LICENSE) have been removed from the css/blueprint directory. This change eliminates the legacy grid, typography, and form styling provided by Blueprint, aligning with the project's shift to use Bootstrap as the primary CSS framework.

css/blueprint · high confidence

Removal of bundled CodeMirror editor assets

The theme has removed the bundled CodeMirror JavaScript and CSS files located in the includes directory. This deletion removes the embedded code editor functionality and its associated syntax highlighting styles from the product.

includes · high confidence

Removal of legacy theme styles

The file css/style.css has been deleted, removing all custom styling for the theme's layout, navigation, forms, and typography. This eliminates the previous visual presentation defined in this stylesheet, which included specific grid, header, and content styles.

css · high confidence

Behavioural changes

Initialize JavaScript entry points for Vite build

The \resources/js\ directory now contains the initial JavaScript entry points (\app.js\ and \editor.js\) required for the new Vite-based build system. \app.js\ serves as the main application entry, while \editor.js\ initializes the WordPress block editor environment using the \@wordpress/dom-ready\ package to ensure scripts run after the DOM is ready.

resources/js · high confidence

New Blade view partials for content, comments, and metadata

The theme now uses dedicated Blade view partials in \resources/views/partials\ to render site components, replacing previous inline or template-based approaches. These include \content.blade.php\ and \content-single.blade.php\ for post listings and single posts (with the latter adopting h-entry microformat classes like \h-entry\ and \p-name\), \comments.blade.php\ for the comment section and form, \entry-meta.blade.php\ for publication date and author information, \content-page.blade.php\ for page content and pagination, \content-search.blade.php\ for search results, and \page-header.blade.php\ for page titles. This structure centralizes the HTML output for these elements, improving maintainability and consistency across the theme's rendering logic.

resources/views/partials · high confidence

New Blade view templates for Sage 10 compatibility

The application now uses a new set of Blade view templates (404, index, page, search, single, and template-custom) to support the Sage 10 theme architecture. These views define the structure for standard WordPress page types, including handling post loops, displaying search forms and alerts when no results are found, and rendering post navigation. The index and search templates explicitly include a sidebar section via a partial, while single and page templates focus on content rendering using specific partials based on post type.

resources/views · high confidence

New ThemeServiceProvider for Sage 10 integration

A new ThemeServiceProvider has been added to the application, extending Roots\\Acorn\\Sage\\SageServiceProvider. This change supports the migration to Sage 10 and Acorn v3, ensuring that theme-specific service registrations and bootstrapping are handled through the Sage provider hierarchy rather than the default Laravel service provider.

app/Providers · high confidence

New app layout with accessibility and Tailwind integration

The main application layout has been updated to include a 'Skip to content' link for improved keyboard accessibility and integrates Tailwind CSS via Vite. The structure now explicitly includes header and footer sections, a main content area, and an optional sidebar, while ensuring WordPress hooks like wp\_head and wp\_body\_open are correctly positioned.

resources/views/layouts · high confidence

New theme setup and filter configuration

The theme now includes a new \app/setup.php\ file that configures core WordPress features, including registering primary navigation menus, enabling post thumbnails, responsive embeds, HTML5 markup support, and selective refresh for widgets. It also registers two sidebars (Primary and Footer) and disables full-site editing support by removing \block-templates\ and \core-block-patterns\ theme support. Additionally, \app/filters.php\ adds a filter to append a 'Continued' link to post excerpts. The setup also integrates Vite for the block editor, injecting editor styles and scripts, and disables on-demand block asset loading.

app · high confidence

Refactor site layout into modular section views

The site's layout structure has been reorganized by extracting the header, footer, and sidebar into dedicated view files within the \resources/views/sections\ directory. This change introduces a new header component that renders the site name and primary navigation menu, a footer component that displays the footer sidebar, and a sidebar component for the primary sidebar. This modularization separates distinct layout parts, improving maintainability of the page structure.

resources/views/sections · high confidence

Refactor view data composition into dedicated Composer classes

View logic for site metadata, post content, and comments has been moved from templates into dedicated Composer classes (App, Post, and Comments). This change centralizes how data like the site name, post titles, pagination, and comment lists are prepared for the Blade views, ensuring consistent data availability across templates and simplifying template markup by removing procedural PHP logic from the view files.

app/View · high confidence

Removed bundled jQuery plugins and switched to HTML5 Boilerplate script structure

The project has removed several locally bundled jQuery plugins—specifically jquery.cycle.lite.min.js, jquery.cycle.min.js, jquery.fancybox-1.3.4.pack.js, and jquery.placeholder.min.js—and deleted the custom scripts.js file. These changes align with the adoption of the HTML5 Boilerplate setup, which manages plugin dependencies via its own plugins.js and script.js files rather than maintaining local copies of these libraries.

js · high confidence

Upgrade to Tailwind CSS v4 with explicit source configuration

The project has upgraded to Tailwind CSS v4, replacing the previous CSS setup. The new \app.css\ entry point uses the Tailwind v4 import syntax and explicitly defines source globs for PHP, Blade, and JavaScript files to ensure utility classes are generated correctly. A new \editor.css\ file has been added to handle styling for the editor component, also leveraging the updated Tailwind import.

resources/css · high confidence

Fixes

Added .gitkeep to public directory

A .gitkeep file has been added to the public directory to ensure the folder is tracked by version control, preventing missing folder errors when running the development server.

public · high confidence

Dependencies

Upgrade to Vite 8 and Tailwind CSS 4

The build system has been upgraded to use Vite 8 and Tailwind CSS 4, replacing previous versions. This change requires Node.js version 20.19.0+ or 22.12.0+ and updates the PHP minimum requirement to 8.3. The \package.json\ now lists \vite\, \tailwindcss\, \@roots/vite-plugin\, \@tailwindcss/vite\, and \laravel-vite-plugin\ as dev dependencies, while \composer.json\ requires \roots/acorn\ ^6.0 and \laravel/pint\ ^1.20.

(dependencies) · high confidence

Upgraded jQuery to version 1.5.2

The jQuery library in js/libs has been updated from version 1.5.1 to 1.5.2. This upgrade replaces the existing minified script file, bringing in the latest bug fixes and improvements included in the new release.

js/libs · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 49 → 47 (-2.1)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 71 → 54 (-16.5)
  • Architecture 69 → 69 (+0.0)
  • Maturity 48 → 48 (+0.0)
  • Readiness 39 → 39 (+0.0)
  • Security 65 → 56 (-8.8)
  • Accessibility 80 → 100 (+19.7)

Resolved (4)

  • No ADRs found
  • No tests found
  • Scanner failed to run — not a clean result
  • Scanner failed to run — not a clean result

New (2)

  • Documentation: no build, run or usage example (README.md)
  • No ADRs found (package.json)

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

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 a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 13 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 7f53bafdf528f7e3270f4f6837beabcca223514c — the exact code this score is about.
  • Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.64+preprod-569132d3dfbe.