Current Behavior
The Makefiles for any repository subscribed to the meshery-academy topic should follow a single standard for their main recipes. As it stands, most of these repos don't follow a canonical approach, and their Makefiles have diverged from one another.
The core problem is inconsistent handling of the Hugo binary. Some recipes invoke a globally installed hugo, while others rely on the Node-managed instance installed into node_modules via hugo-extended. These two are not interchangeable: a bare hugo call in a Make recipe resolves through the system PATH and will not find the Node-local binary, whereas the dependency check (check-deps) specifically verifies that hugo exists at node_modules/.bin/hugo. As a result, recipes that pass the dependency check can still run the wrong Hugo, and recipes gated by that check can fail even when a usable Hugo is present.
This inconsistency causes the Upgrade Academies workflow to fail, since it runs make theme-update across every dependent repo and expects uniform behavior. Standardizing the Makefiles so that all repos provision and invoke Hugo the same way is needed to make the recipes — and the automated theme bump — work reliably across the board.
Contributor Guide and Resources
Current Behavior
The Makefiles for any repository subscribed to the meshery-academy topic should follow a single standard for their main recipes. As it stands, most of these repos don't follow a canonical approach, and their Makefiles have diverged from one another.
The core problem is inconsistent handling of the Hugo binary. Some recipes invoke a globally installed hugo, while others rely on the Node-managed instance installed into node_modules via hugo-extended. These two are not interchangeable: a bare hugo call in a Make recipe resolves through the system PATH and will not find the Node-local binary, whereas the dependency check (check-deps) specifically verifies that hugo exists at node_modules/.bin/hugo. As a result, recipes that pass the dependency check can still run the wrong Hugo, and recipes gated by that check can fail even when a usable Hugo is present.
This inconsistency causes the Upgrade Academies workflow to fail, since it runs make theme-update across every dependent repo and expects uniform behavior. Standardizing the Makefiles so that all repos provision and invoke Hugo the same way is needed to make the recipes — and the automated theme bump — work reliably across the board.
Contributor Guide and Resources