Repository navigation
Move the conformance statement into the docs Guides category - #89
Merged
Merged
Conversation
The docs site's deploy-build IA gate grades each package's current release sidebar, and the sidebar on main would fail it the moment it ships in a release: IA040 mllp: top-level category "Conformance" is not on the canonical spine (reproduced with the site's own lint over `pnpm pack:docs` output at 9c339c1). A red gate there stops every docs.cosyte.com deploy, not only this package's pages, and this is the sidebar the next release would pack. The site allows only Overview, Installation, Quickstart, Core Concepts, Guides and Troubleshooting as top-level category labels, and a label after Troubleshooting has no canonical home. The statement moves into Guides after the testing page, which is where @cosyte/ccda already keeps its conformance page. The docs structure test requires sidebar_position to ascend in sidebar order, so the statement takes 9 and the limitations page, now last, takes 10. The statement stays in the sidebar, and no page id, file name or URL changes. No changeset: docs-content/ is not in the npm tarball, so the published package does not 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
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.
The docs site's deploy-build IA gate grades each package's current release sidebar, and the sidebar on
mainwould fail it as soon as it ships in a release. Reproduced with the site's own lint overpnpm pack:docsoutput at 9c339c1:A red gate there stops every docs.cosyte.com deploy, not only this package's pages (cosyte/docs Dispatch receiver run 36196140266 is the same failure for three other packages), and this is the sidebar the next release packs.
What changes
The conformance statement moves from its own top-level category into Guides, after the testing page. That is where
@cosyte/ccdaalready keeps its conformance page.test/docs/structure.test.tsrequiressidebar_positionto ascend in sidebar order, so the statement takes 9 and the limitations page, now last, takes 10. The statement stays in the sidebar, and no page id, file name or URL changes.Top level after:
intro, Installation, Quickstart, Core Concepts, Guides, TroubleshootingVerification
runLint(strict) overpnpm pack:docsoutput staged as the current version slot: base reproduces the error, this branch reportsOK: all checked packages conform to the IA spine.pnpm test(includingtest/docs/structure.test.tsandtest/conformance/statement.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.https://claude.ai/code/session_01U24bnHKNxQWMxmfN7ny7w9