Skip to content

docs: restructure user nav into groups; move dev docs to repo#449

Open
jamesvillarrubia wants to merge 2 commits into
developfrom
docs/restructure-user-nav
Open

docs: restructure user nav into groups; move dev docs to repo#449
jamesvillarrubia wants to merge 2 commits into
developfrom
docs/restructure-user-nav

Conversation

@jamesvillarrubia

Copy link
Copy Markdown
Collaborator

Restructure the user docs navigation

The docs site is the product manual for people using Pipecraft, so the menu now contains only user-facing pages, grouped by intent. Developer/internal material moves to the repo (linked from the README).

Before → after

Flat list of 18 → 5 groups:

Get started   Introduction · Quickstart
Guides        Workflow generation · Workflow patterns · Versioning · Examples
Reference     CLI reference · Configuration · Action modes
Understand    Architecture
Help          Troubleshooting · Error reference · FAQ · Roadmap · Security

Clarity fixes

  • Commands vs CLI Reference — recast the overlap: commands is now the CLI reference (Reference group); the task walkthrough cli-reference becomes Quickstart (Get started). No content lost; clear distinct roles.
  • Dropped the inconsistent PipeCraft title prefix (e.g. "PipeCraft Error Handling Guide" → "Error reference").

Developer docs → repo (out of the user site)

  • testing-guide.mddocs-dev/testing.md
  • ast-operations.mddocs-dev/ast-operations.md (generator internals)
  • contributing.md removed (root CONTRIBUTING.md already exists)
  • removed orphan docs-index.md / readme.md (README is canonical)
  • API Reference (generated typedoc) dropped from the nav; the pages are kept so the ~11 inbound cross-links still resolve. Follow-up: fully relocating the generated output to a dev space is a build-config change.
  • README now points contributors at CONTRIBUTING.md + docs-dev/.

Safety

Sidebar uses custom labels, so heavily cross-linked file ids (commands ×16, api ×11) are unchanged → no broken links. pnpm docs:build passes; the 2 genuinely broken links from the moves (faq→contributing, error-reference→testing) were repointed.

Heads up: this is a navigation/UX change worth eyeballing rendered (cd docs && pnpm start). Not auto-merging — review the nav and merge when it looks right.

🤖 Generated with Claude Code

jamesvillarrubia and others added 2 commits June 20, 2026 13:58
The docs site is the product manual for people USING Pipecraft. Flatten-list of 18
items -> 5 intent-based groups (Get started / Guides / Reference / Understand / Help),
and remove developer/internal material from the user nav.

User nav:
- Get started: Introduction, Quickstart (recast cli-reference — 0 inbound links)
- Guides: Workflow generation, Workflow patterns, Versioning, Examples
- Reference: CLI reference (was Commands), Configuration, Action modes
- Understand: Architecture (kept — it's user-facing)
- Help: Troubleshooting, Error reference (de-prefixed), FAQ, Roadmap, Security

Developer/internal -> repo (linked from README):
- testing-guide.md -> docs-dev/testing.md
- ast-operations.md -> docs-dev/ast-operations.md (internals)
- contributing.md removed (CONTRIBUTING.md already exists at root)
- removed orphan docs-index.md / readme.md (README is canonical)
- API Reference (generated typedoc) dropped from the nav; pages kept so the ~11
  inbound cross-links still resolve (fully relocating generated output is a follow-up)

Sidebar uses custom labels so heavily-linked file ids (commands x16, api x11) are
unchanged — no broken links. docs build passes; the 2 real broken links from the moves
(faq->contributing, error-reference->testing) repointed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- init is non-interactive by default (--interactive opts into the wizard); drop the
  stale package-manager auto-detection prompts (packageManager is deprecated)
- add the missing 'pipecraft setup' step (creates the branch flow on the remote) —
  its absence is why promotions fail with 'Base ref must be a branch'
- clarify setup (branches) vs setup-github (permissions); fix example step numbering
- minimal config example: add required mergeStrategy/requireConventionalCommits/semver
  and use prefixes instead of deprecated testable/deployable

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jamesvillarrubia jamesvillarrubia enabled auto-merge (squash) June 25, 2026 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant