feat(docs): surface Garlemald-Client contributor docs under Contributing#4
Merged
Merged
Conversation
Wire the new Garlemald-Client contributor docs (architecture, developer environment, AI-agent guides, CONTRIBUTING, CLAUDE.md, AGENTS.md, releasing) into the client project's Docs tab via the existing scalable `group: "Contributing"` mechanism — the same one already used for Garlemald-Server. Registry-only change: tag the client's docs with `group: "Contributing"` in src/data/registry.mjs. The Docs-tab grouping, fetch pipeline, and routes are already in place, so no code changes are needed. content.json is intentionally not regenerated here; the deploy workflow + daily cron rebake it. The client docs land on `develop` via Garlemald-Client#27 and appear here automatically on the next build (fetch-content fails soft on the 404 until then). Verified: registry parses; `npm run typecheck` clean; `npm run build` static-exports. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wires the new Garlemald-Client contributor docs into the Garlemald Client project page's Contributing section — using the same scalable
group: "Contributing"mechanism already shipped for Garlemald-Server (site #1).Change
Registry-only. Tag the client's docs with
group: "Contributing"insrc/data/registry.mjs:CONTRIBUTING.md,docs/architecture.md,docs/dev-environment.md,docs/agents.md,CLAUDE.md,AGENTS.md,docs/RELEASING.md→ Contributingws2_32-proxy/README.md,NOTICE.md,LICENSE.mdstay in the default Reference section.The Docs-tab grouping UI, the fetch pipeline (
groupcarried throughfetch-content.mjs), and the routes were all added with the server work — so no code changes are needed here. This is exactly the "add another project later with a one-line-per-doc registry change" path that mechanism was built for.Validation
npm run typecheckclean;npm run buildstatic-exports all pages.content.jsonintentionally not regenerated — the deploy workflow + daily cron rebake it. The client docs land ondevelopvia Garlemald-Client#27;fetch-contentfails soft on the 404 until then, so the section populates on the next build after that merge.🤖 Generated with Claude Code