PHPackages                             kimhf/sage-woocommerce-support - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Templating & Views](/categories/templating)
4. /
5. kimhf/sage-woocommerce-support

ActiveLibrary[Templating & Views](/categories/templating)

kimhf/sage-woocommerce-support
==============================

Add Woocommerce blade template and controllers support for Sage 9 based themes.

v9.0.4(7y ago)11995↓100%1MITPHPPHP >=7.1

Since May 5Pushed 6y ago3 watchersCompare

[ Source](https://github.com/kimhf/sage-woocommerce-support)[ Packagist](https://packagist.org/packages/kimhf/sage-woocommerce-support)[ RSS](/packages/kimhf-sage-woocommerce-support/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (5)Dependencies (1)Versions (8)Used By (0)

Sage Woocommerce Support
========================

[](#sage-woocommerce-support)

Add Woocommerce blade template and controllers support for Sage 9 based themes.

Installation
------------

[](#installation)

Run inside theme directory.

`composer require kimhf/sage-woocommerce-support`

Requirements
------------

[](#requirements)

PHP 7.1 or above

Usage
-----

[](#usage)

Example: To override the template `plugins/woocommerce/templates/single-product.php` create `themes/yoursagetheme/resources/views/single-product.blade.php` or `themes/yoursagetheme/resources/views/woocommerce/single-product.blade.php`

Example: To override the partial `plugins/woocommerce/templates/content-product.php` create `themes/yoursagetheme/resources/views/partials/content-product.blade.php` or `themes/yoursagetheme/resources/views/woocommerce/content-product.blade.php` or `themes/yoursagetheme/resources/views/content-product.blade.php`

Details
-------

[](#details)

The package will look for templates in the paths defined in the Sage config `view.paths`. It will search for both .php and .blade.php files.

Data from controllers and args from woocommerce will always be added to blade templates, even if you mix usage between php and blade templates.

### With default Sage and WooCommerce config:

[](#with-default-sage-and-woocommerce-config)

A template from the template hierarchy will loaded from `resources/views/woocommerce` or `resources/views` as entry template. (WC\_Template\_Loader will only load the empty resources/index.php in this case.)

`wc_get_template()` Will with default config look inside `resources/views/woocommerce` and `resources/views`. $args added by Woocommerce will take priority over controller data if there are any conflicts.

`wc_get_template_part()` Will with default config look inside `resources/views/woocommerce`, `resources/views/partials` and `resources/views`.

`wc_get_template_html()` Is not supported.

###  Health Score

32

—

LowBetter than 72% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity63

Established project with proven stability

 Bus Factor1

Top contributor holds 96.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~43 days

Total

5

Last Release

2754d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/a00d52f7ff25b8e542e241923b9a1de220dc97391a20cab62bcf96f7a5957d83?d=identicon)[kimhf](/maintainers/kimhf)

---

Top Contributors

[![kimhf](https://avatars.githubusercontent.com/u/1223194?v=4)](https://github.com/kimhf "kimhf (29 commits)")[![dsturm](https://avatars.githubusercontent.com/u/384815?v=4)](https://github.com/dsturm "dsturm (1 commits)")

---

Tags

wordpressbladethemewoocommercesage

###  Code Quality

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/kimhf-sage-woocommerce-support/health.svg)

```
[![Health](https://phpackages.com/badges/kimhf-sage-woocommerce-support/health.svg)](https://phpackages.com/packages/kimhf-sage-woocommerce-support)
```

###  Alternatives

[log1x/sage-directives

A set of Blade directives for use with Roots Sage.

297709.3k5](/packages/log1x-sage-directives)[roots/acorn

Framework for Roots WordPress projects built with Laravel components.

9682.1M97](/packages/roots-acorn)[log1x/blade-svg-sage

Composer package to add support for Blade SVG by Adam Wathan to Roots Sage.

7577.3k](/packages/log1x-blade-svg-sage)[hexbit/sage-woocommerce

Woocommerce support for sage 10

257.0k](/packages/hexbit-sage-woocommerce)[roots/wp-blade-check

Simple Composer package that checks and displays an admin notice if your uncompiled Blade templates are publicly accessible.

161.1k](/packages/roots-wp-blade-check)[benjaminmedia/wp-polylang-theme-strings

Polylang Theme Strings with support for Blade syntax

159.9k](/packages/benjaminmedia-wp-polylang-theme-strings)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)