Documentation audit
Audit date: 2026-05-29
Scope
This audit checked the current checkpoint repository against the docs in this
repository. checkpoint is a Docusaurus documentation portal; it does not contain
the BitView application, backend, on-chain, or identity service source trees that
many product docs describe.
Current repository architecture
- Docusaurus 3.10 site configured by
docusaurus.config.js. - React 19 landing page in
src/pages/index.tsx. - Tailwind CSS v4 is loaded through the custom PostCSS plugin in
docusaurus.config.jsand global imports insrc/css/custom.css. - The primary docs plugin serves
docs/at/docswith an autogenerated sidebar fromsidebars.js. - A second
@docusaurus/plugin-content-docsinstance servesguides/at/guideswith an autogenerated sidebar fromsidebars-guides.js. - Docusaurus blog content in
blog/is served at/blog. - Static assets under
static/are copied into the build output. - The only repository-specific environment switch is
BUILD_PUBLIC=true, which excludesdocs/_internal/**from the primary docs plugin before sidebar and route generation.
Findings
Accurate
package.jsonaccurately lists the available Docusaurus scripts:start,start:public,build,build:public,build:internal,serve,deploy,clear,typecheck, and Docusaurus helper scripts.docusaurus.config.jsaccurately implements the public/internal split withBUILD_PUBLIC=trueandexclude: ["**/_internal/**"]for public builds.- The docs and guides sidebars are autogenerated from file structure.
- The documented public docs routes (
/docs,/guides,/blog) match the Docusaurus configuration. - Internal docs can safely link to public docs, and public docs should not link
directly to
docs/_internal/**because those routes are absent from public builds.
Wrong, missing, or outdated
README.mdsaid the site was built with Docusaurus 2; the current dependency is Docusaurus 3.10.README.mdonly documented the default local start/build commands and omitted the public/internal build modes,BUILD_PUBLIC=true, the separate guides docs plugin, the blog route, and the current content layout.docs/_internal/README.mdusednpm run ...examples even though the repo is pinned topnpm@8.15.8viapackageManagerand all top-level docs use pnpm.- One public identity page linked directly to an internal
_internaldocument; the public build excludes that target, so the link was replaced with plain text pointing readers to the internal doc by path. pnpm typecheckcurrently fails before checking site source because the TypeScript configuration references missing type packages (@docusaurus/theme-classicandnode) and TypeScript 6 reports the deprecatedbaseUrloption. This is a repository configuration issue, not a docs-command issue; the build commands still succeed.
Fixes made
- Updated
README.mdto describe Docusaurus 3, Node/pnpm requirements, install/start/build commands, public/internal build behavior, routes, and content layout. - Updated
docs/_internal/README.mdexamples fromnpm run ...topnpm ...and corrected the public-build leakage check to assert that no generatedbuild/docs/_internalroute exists. - Updated the operations page's documentation-site deploy section to use the current Docusaurus 3 public/internal build commands.
- Removed the direct public-to-internal markdown link in
docs/technical/identity.mdwhile preserving the internal reference by path. - Added this audit report.
Verification
Commands run from repository root:
corepack pnpm --version
corepack pnpm typecheck
corepack pnpm build
corepack pnpm build:public
test ! -e build/docs/_internal && echo 'public-build-no-internal-route: clean'
Results:
corepack pnpm --versionreported8.15.8.corepack pnpm buildsucceeded and generatedbuild/.corepack pnpm build:publicsucceeded and generatedbuild/withBUILD_PUBLIC=true.- The public build did not generate a
build/docs/_internalroute. corepack pnpm typecheckfailed with existing TypeScript configuration/type dependency errors: missing@docusaurus/theme-classictypes, missingnodetypes, and TS5101 for deprecatedbaseUrlunder TypeScript 6.