Repository navigation
Put the docs sidebar back on the docs site's section spine - #156
Merged
Merged
Conversation
docs.cosyte.com cannot deploy while @cosyte/dicom 0.1.0 is the current release: the site's deploy-build IA gate grades each package's current release sidebar, and this one fails it (cosyte/docs Dispatch receiver run 36196140266): IA040 dicom@v0.1.0: top-level category "Diagnosing & limits" is not on the canonical spine IA060 dicom@v0.1.0: missing first-use entry "Installation" IA060 dicom@v0.1.0: missing first-use entry "Quickstart" The site allows only Overview, Installation, Quickstart, Core Concepts, Guides and Troubleshooting as top-level category labels, in that order, and requires top-level Installation and Quickstart categories that reach a doc. This package's own structure test forbids a category whose label repeats the name of any page, which is why the installation and quickstart pages sat at the top level as bare docs. Both rules hold now: the canonical categories are back, and the three pages whose title or sidebar label matched a category label are renamed: installation: "Installation" becomes "Install and verify" quickstart: "Quickstart" becomes "Read your first DICOM object" (sidebar "Your first object") troubleshooting: sidebar label "Troubleshooting" becomes "Symptoms and causes" "Diagnosing & limits" becomes Troubleshooting with the same two pages. Page ids, file names and URLs do not change, so every inbound link still resolves. No changeset: docs-content/ is not in the npm tarball, so the published package does not change. The fix reaches the site through the v0.1.0 release's docs-content.tar.gz, repacked from the release commit plus this change. Claude-Session: https://claude.ai/code/session_01U24bnHKNxQWMxmfN7ny7w9
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.
docs.cosyte.com cannot deploy while
@cosyte/dicom0.1.0 is the current release. The site's deploy-build IA gate (cosyte/docs Dispatch receiver run 36196140266) grades each package's current release sidebar, and this one fails it:What changes
Top level before:
intro, installation (bare doc), quickstart (bare doc), Core Concepts, Guides, Diagnosing & limitsTop level after:
intro, Installation, Quickstart, Core Concepts, Guides, TroubleshootingThis package's own
docs-content-structuretest forbids a category whose label repeats the name of any page, so the three pages whose title or sidebar label matched a category label are renamed:installationquickstarttroubleshootingPage ids, file names and URLs do not change, so every inbound link still resolves.
Verification
runLint(fromcosyte/docsscripts/check-ia-conformance.ts, strict mode) overpnpm pack:docsoutput staged as the current version slot: base reproduces the three errors above, this branch reportsOK: all checked packages conform to the IA spine. The fetcher's sidebar doc-id validation passes too.pnpm test(includingtest/docs-content-structure.test.ts),pnpm format:check,pnpm check:no-emdash,pnpm check:no-internal-refs,pnpm phi-scan, and the shareddocs-content-check.mjs: all green locally.No changeset:
docs-content/is not in the npm tarball, so the published package does not change. The fix reaches the site through the v0.1.0 release'sdocs-content.tar.gz, repacked from the release commit plus this change.https://claude.ai/code/session_01U24bnHKNxQWMxmfN7ny7w9