fix: restore readable docs site layouts and copy

Author: stiwicourage

CHANGELOG.md

@@ -15,6 +15,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ### Fixed
 
+- Website layout and copy now keep expanding with the browser width instead of stopping at fixed max-width caps on wide windows; the shared site stylesheet no longer limits the outer page shell, guide intros, leads, section headings, or guide body text to narrow fixed widths.
+- The command cheat sheet now keeps the "Set up a project" section balanced by summarizing scaffold extras instead of repeating the full internal Agentic guidance list.
+- The getting-started guide now splits the Agentic quickstart explanation into shorter paragraphs so the scaffold flow stays readable on the site.
+- The core workflows guide now splits the scaffold and Agentic starter explanation into shorter paragraphs so the page stays readable on the site.
+- The command cheat sheet now stacks the three "Set up a project" cards vertically so the section reads top-to-bottom without a missing grid slot.
+
 ### Security
 
 ## [3.0.0] - 2026-05-17
@@ -417,4 +423,3 @@ This release was yanked because it removed the implicit `Pester` dependency, bef
 [0.0.6]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.5...Version_0.0.6
 [0.0.5]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.4...Version_0.0.5
 [0.0.4]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.3...Version_0.0.4
-

docs/assets/site.css

@@ -11,7 +11,7 @@
     --outline: rgba(255, 255, 255, 0.12);
     --shadow: 0 20px 60px rgba(0, 0, 0, 0.28);
     --radius: 22px;
-    --max-width: 1600px;
+    --max-width: none;
     --anchor-offset: 2.90rem;
 }
 
@@ -254,7 +254,7 @@ pre code {
 
 .guide-hero {
     margin-bottom: 3rem;
-    max-width: 880px;
+    max-width: none;
 }
 
 
@@ -331,7 +331,7 @@ pre code {
 .guide-content .content-section > p,
 .guide-content .content-section > ul,
 .guide-content .content-section > ol {
-    max-width: 72ch;
+    max-width: none;
 }
 
 .guide-grid {
@@ -380,7 +380,7 @@ h3 {
 
 h1 {
     font-size: clamp(2.6rem, 5vw, 4.6rem);
-    max-width: 12ch;
+    max-width: none;
 }
 
 h2 {
@@ -398,7 +398,7 @@ p {
 
 .lead {
     font-size: 1.1rem;
-    max-width: 68ch;
+    max-width: none;
 }
 
 .hero__actions {
@@ -517,11 +517,11 @@ p {
 }
 
 .narrow {
-    max-width: 760px;
+    max-width: none;
 }
 
 .section-heading {
-    max-width: 760px;
+    max-width: none;
     margin-bottom: 2.5rem;
 }
 
@@ -772,6 +772,10 @@ td {
     gap: 1.5rem;
 }
 
+.command-card-grid--stacked {
+    grid-template-columns: 1fr;
+}
+
 .command-card h3 {
     margin-bottom: 0.75rem;
 }

docs/commands.html

@@ -89,7 +89,7 @@ <h1>Keep one workflow surface in view</h1>
             <h2>On this page</h2>
             <ul class="toc-list">
                 <li><a href="#choose-surface">Choose your surface</a></li>
-                <li><a href="#setup-and-project">Setup and project</a></li>
+                <li><a href="#setup-and-project">Set up a project</a></li>
                 <li><a href="#build-and-validate">Build and validate</a></li>
                 <li><a href="#package-and-ship">Package and ship</a></li>
                 <li><a href="#version-and-update">Version and update</a></li>
@@ -146,8 +146,8 @@ <h2>Choose your surface</h2>
             </section>
 
             <section class="content-section" id="setup-and-project">
-                <h2>Setup and project</h2>
-                <div class="command-card-grid">
+                <h2>Set up a project</h2>
+                <div class="command-card-grid command-card-grid--stacked">
                     <article class="command-card">
                         <h3>Install the <code>nova</code> launcher</h3>
                         <p>Use this one-time PowerShell setup when you want <code>nova</code> available directly from
@@ -174,37 +174,16 @@ <h3>Start a new project</h3>
                         <div class="surface-note" data-command-visibility="powershell">
                             <p><strong>Cmdlet:</strong> <code>Initialize-NovaModule</code></p>
                         </div>
-                        <p>Create the minimal scaffold or the example scaffold for a new module project. Before the
-                            first interactive question, Nova checks whether a newer NovaModuleTools release is
-                            available and warns without blocking the scaffold flow. When Git is enabled, Nova also
-                            creates or updates a default <code>.gitignore</code> in the generated project root so
-                            common local and CI artifact paths are ignored without overwriting existing rules. Both
-                            interactive flows can also add the optional Agentic Copilot starter package,
-                            which follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test
-                            expectations, <code>project.json</code> <code>Manifest.PowerShellHostVersion</code>
-                            compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated
-                            <code>dist</code> module files, command-help ownership, source-mirrored test guidance,
-                            instructions to fix ScriptAnalyzer findings reported by <code>run.ps1</code> before
-                            handoff, explicit public/private PowerShell file ownership guidance, a best-effort
-                            source/helper-script maintainability guidance plus separate test-design guidance delivered
-                            through best-effort source/helper-script maintainability guidance plus separate test-design guidance, explicit PSScriptAnalyzer
-                            workflow guidance for <code>./scripts/build/Invoke-ScriptAnalyzerCI.ps1</code>,
-                            <code>./run.ps1</code>, focused <code>Invoke-ScriptAnalyzer</code> usage, and
-                            Test-NovaBuild-only project test guidance that forbids direct
-                            <code>Invoke-Pester</code>, explicit
-                            valid-PlatyPS help guidance for <code>docs/&lt;ProjectName&gt;/en-US/*.md</code> using
-                            <code>New-MarkdownCommandHelp</code>, <code>Update-MarkdownCommandHelp</code>, and
-                            <code>Test-MarkdownCommandHelp</code>, with a matching help file required for every new
-                            public entry point, and a strict file-ending rule for changed or
-                            generated text files.
-                        </p>
-                        <p>New projects also start with Nova's default <code>Pester.CodeCoverage</code> block in
-                            <code>project.json</code>, but keep it disabled until you choose to enable coverage.</p>
-                        <p>If you enable the Agentic package, Nova also asks for a short project name used in generated
-                            guidance placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the
-                            short name is <code>Nova</code>, but it could also have been <code>NMT</code>.</p>
+                        <p>Create the minimal scaffold or the example scaffold for a new module project.</p>
                         <ul class="plain-list">
                             <li><strong>Use when:</strong> you are creating a fresh NovaModuleTools project</li>
+                            <li><strong>Includes:</strong> a pre-question Nova release warning, best-effort
+                                <code>.gitignore</code> creation or update when Git is enabled, and Nova's default
+                                <code>Pester.CodeCoverage</code> block in <code>project.json</code> with coverage still
+                                disabled until you choose to turn it on</li>
+                            <li><strong>Optional:</strong> add the <strong>Agentic Copilot</strong> starter package for Nova-maintained
+                                build, test, analyzer, help, and guidance files; if you enable it, Nova also asks for a
+                                short project name for placeholders such as <code>Invoke-&lt;ShortName&gt;*</code></li>
                             <li data-command-visibility="command-line" hidden><strong>Remember:</strong> pass the target path
                                 explicitly with <code>--path</code> or <code>-p</code></li>
                             <li data-command-visibility="powershell"><strong>Common parameters:</strong>

docs/core-workflows.html

@@ -123,31 +123,29 @@ <h2>Create the project</h2>
                     <p>Use <code>% nova init --path ~/Work</code> or <code>% nova init -p ~/Work</code>, not positional
                         path syntax such as <code>% nova init ~/Work</code>.</p>
                 </div>
-                <p>Both scaffold styles ask the same core project questions, and both now offer an optional Agentic
-                    Copilot starter package after the Git prompt. The starting version prompt now defaults to
-                    <code>0.1.0-preview</code>, so new projects begin on Nova's prerelease-friendly starter line unless
-                    you choose a different version. Before the first question, Nova also checks whether a
-                    newer NovaModuleTools release is available and warns without blocking the scaffold flow. When you
-                    enable Git in either scaffold style, Nova also creates or updates a default <code>.gitignore</code>
-                    in the generated project root so common local and CI artifact paths are ignored without
-                    overwriting existing rules. The Agentic prompt defaults to <code>No</code>, and the package
-                    follows Nova's maintained agentic guidance through a
-                    filtered starter mirror, including
-                    Nova build/test/package expectations, <code>project.json</code>
-                    <code>Manifest.PowerShellHostVersion</code> compatibility guidance, strict ScriptAnalyzer guidance
-                    without excluded rules, generated <code>dist</code> module files, command-help ownership,
-                    source-mirrored test guidance, instructions to fix ScriptAnalyzer findings reported by
-                    <code>run.ps1</code> before handoff, explicit public/private PowerShell file ownership guidance, a
-                    best-effort source/helper-script maintainability guidance plus separate test-design guidance
-                    delivered through Agentic Copilot guidance files, explicit PSScriptAnalyzer workflow
-                    guidance for <code>./scripts/build/Invoke-ScriptAnalyzerCI.ps1</code>, <code>./run.ps1</code>, and
-                    focused <code>Invoke-ScriptAnalyzer</code> usage, Test-NovaBuild-only project test guidance that
-                    forbids direct <code>Invoke-Pester</code>, explicit valid-PlatyPS help guidance for
-                    <code>docs/&lt;ProjectName&gt;/en-US/*.md</code> using
+                <p>Both scaffold styles ask the same core project questions, and both now offer an optional
+                    <strong>Agentic Copilot</strong> starter package after the Git prompt.</p>
+                <p>The starting version prompt now defaults to <code>0.1.0-preview</code>, so new projects begin on
+                    Nova's prerelease-friendly starter line unless you choose a different version. Before the first
+                    question, Nova also checks whether a newer NovaModuleTools release is available and warns without
+                    blocking the scaffold flow. When you enable Git in either scaffold style, Nova also creates or
+                    updates a default <code>.gitignore</code> in the generated project root so common local and CI
+                    artifact paths are ignored without overwriting existing rules.</p>
+                <p>The Agentic prompt defaults to <code>No</code>, and the package follows Nova's maintained agentic
+                    guidance through a filtered starter mirror, including Nova build/test/package expectations,
+                    <code>project.json</code> <code>Manifest.PowerShellHostVersion</code> compatibility guidance,
+                    strict ScriptAnalyzer guidance without excluded rules, generated <code>dist</code> module files,
+                    command-help ownership, source-mirrored test guidance, instructions to fix ScriptAnalyzer findings
+                    reported by <code>run.ps1</code> before handoff, explicit public/private PowerShell file ownership
+                    guidance, a best-effort source/helper-script maintainability guidance plus separate test-design
+                    guidance delivered through <strong>Agentic Copilot</strong> guidance files, explicit
+                    PSScriptAnalyzer workflow guidance for <code>./scripts/build/Invoke-ScriptAnalyzerCI.ps1</code>,
+                    <code>./run.ps1</code>, and focused <code>Invoke-ScriptAnalyzer</code> usage, Test-NovaBuild-only
+                    project test guidance that forbids direct <code>Invoke-Pester</code>, explicit valid-PlatyPS help
+                    guidance for <code>docs/&lt;ProjectName&gt;/en-US/*.md</code> using
                     <code>New-MarkdownCommandHelp</code>, <code>Update-MarkdownCommandHelp</code>, and
                     <code>Test-MarkdownCommandHelp</code>, with a matching help file required for every new public
-                    entry point, and a strict file-ending rule for changed or generated text
-                    files.</p>
+                    entry point, and a strict file-ending rule for changed or generated text files.</p>
                 <p>The generated <code>project.json</code> also starts with Nova's standard <code>Pester</code>
                     defaults, including a disabled <code>CodeCoverage</code> block with explicit source coverage paths
                     for <code>src/public/</code>, nested <code>src/private/</code> helper folders, and

docs/getting-started.html

@@ -194,31 +194,29 @@ <h2>4. Scaffold the packaged example</h2>
                     </div>
                 </div>
                 <p>Nova asks for the project name, description, version, author, minimum PowerShell version, whether
-                    Git should be initialized, and whether Nova should add the optional Agentic Copilot starter package.
-                    The starting version prompt now defaults to <code>0.1.0-preview</code>, so new projects begin on
-                    Nova's prerelease-friendly starter line unless you choose a different version.
-                    Before the first question, Nova also checks whether a newer NovaModuleTools release is available and
-                    warns without blocking the scaffold flow.
-                    When you enable Git, Nova also creates or updates a default <code>.gitignore</code> in the new
-                    project root so common local and CI artifact paths start ignored without overwriting existing ignore
-                    rules.
-                    The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror,
+                    Git should be initialized, and whether Nova should add the optional <strong>Agentic Copilot</strong> starter package.</p>
+                <p>The starting version prompt now defaults to <code>0.1.0-preview</code>, so new projects begin on
+                    Nova's prerelease-friendly starter line unless you choose a different version. Before the first
+                    question, Nova also checks whether a newer NovaModuleTools release is available and warns without
+                    blocking the scaffold flow. When you enable Git, Nova also creates or updates a default
+                    <code>.gitignore</code> in the new project root so common local and CI artifact paths start ignored
+                    without overwriting existing ignore rules.</p>
+                <p>The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror,
                     including Nova build/test/package expectations, <code>project.json</code>
                     <code>Manifest.PowerShellHostVersion</code> compatibility guidance, strict ScriptAnalyzer guidance
                     without excluded rules, generated <code>dist</code> module files, command-help ownership,
                     source-mirrored test guidance, instructions to fix ScriptAnalyzer findings reported by
                     <code>run.ps1</code> before handoff, explicit public/private PowerShell file ownership guidance, a
                     best-effort source/helper-script maintainability guidance plus separate test-design guidance
-                    delivered through Agentic Copilot guidance files, explicit PSScriptAnalyzer workflow
+                    delivered through <strong>Agentic Copilot</strong> guidance files, explicit PSScriptAnalyzer workflow
                     guidance for <code>./scripts/build/Invoke-ScriptAnalyzerCI.ps1</code>, <code>./run.ps1</code>, and
                     focused <code>Invoke-ScriptAnalyzer</code> usage, Test-NovaBuild-only project test guidance that
                     forbids direct <code>Invoke-Pester</code>, explicit valid-PlatyPS help guidance for
                     <code>docs/&lt;ProjectName&gt;/en-US/*.md</code> using
                     <code>New-MarkdownCommandHelp</code>, <code>Update-MarkdownCommandHelp</code>, and
                     <code>Test-MarkdownCommandHelp</code>, with a matching help file required for every new public
-                    entry point, and a strict file-ending rule for changed or generated text
-                    files.
-                    Nova then creates a project folder under the path you selected.</p>
+                    entry point, and a strict file-ending rule for changed or generated text files.</p>
+                <p>Nova then creates a project folder under the path you selected.</p>
                 <p>The generated <code>project.json</code> also starts with Nova's standard <code>Pester</code>
                     defaults, including an opt-in <code>CodeCoverage</code> block with <code>Enabled=false</code>,
                     explicit source coverage paths for <code>src/public/</code>, nested <code>src/private/</code>