https://www-staging.alwaldend.com/docs/tools/rules_hugo/ Recent content in Rules Hugo on Alwaldend Hugo en https://www-staging.alwaldend.com/docs/tools/rules_hugo/openspec/specs/project-dns/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/tools/rules_hugo/openspec/specs/project-dns/spec/ <h1 id="project-dns-specification">project-dns Specification<a class="td-heading-self-link" href="#project-dns-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Record the retirement of <code>rules_hugo</code> landing infrastructure while preserving its reusable Bazel module.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-keep-landing-infrastructure-retired">Requirement: Keep landing infrastructure retired<a class="td-heading-self-link" href="#requirement-keep-landing-infrastructure-retired" aria-label="Heading self-link"></a></h3><p>The module SHALL follow the <a href="https://www-staging.alwaldend.com/docs/tools/">tools boundary</a> and SHALL have no dedicated landing DNS declarations, Terraform root, or operational source exports.</p> <h4 id="scenario-inspect-the-module-after-landing-retirement">Scenario: Inspect the module after landing retirement<a class="td-heading-self-link" href="#scenario-inspect-the-module-after-landing-retirement" aria-label="Heading self-link"></a></h4><ul> <li><strong>WHEN</strong> the module is consumed from <code>tools/rules_hugo</code></li> <li><strong>THEN</strong> its reusable Bazel rules remain available without landing infrastructure.</li> </ul> https://www-staging.alwaldend.com/docs/tools/rules_hugo/openspec/specs/project-rules-hugo/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/tools/rules_hugo/openspec/specs/project-rules-hugo/spec/ <h1 id="rules-hugo">Rules Hugo<a class="td-heading-self-link" href="#rules-hugo" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Build and run Hugo sites with registered Bazel toolchains, site source archives, and declared PostCSS tooling. This source baseline was observed on 2026-09-08 at revision <code>550d7e79b1f5fdbc2b6017b75178471d6914082f</code>.</p> <p>Sources: <a href="https://www-staging.alwaldend.com/docs/tools/rules_hugo/">project description</a>, <a href="../../../pkg/bzl/al_hugo_site.bzl">site provider rule</a>, <a href="../../../pkg/bzl/al_hugo_run_binary.bzl">build rule</a>, <a href="../../../pkg/bzl/al_hugo_extension.bzl">toolchain extension</a>, and <a href="../../../pkg/bzl/al_hugo_worker.bzl">worker rule</a>.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-separate-site-inputs-from-execution-tools">Requirement: Separate site inputs from execution tools<a class="td-heading-self-link" href="#requirement-separate-site-inputs-from-execution-tools" aria-label="Heading self-link"></a></h3><p><code>al_hugo_site</code> SHALL retain the <code>.tar</code> site archive in the target configuration and resolve its executable PostCSS dependency in the execution configuration. Build rules SHALL obtain Hugo from the registered Hugo toolchain.</p>