How this site uses it
This site (FreeMoCap.github.io) is itself a consumer, and it exercises a narrower slice of the package than the standalone sub-repo sites do:
- Theme CSS.
docusaurus.config.tsloadsrequire.resolve('@freemocap/skellydocs/css/custom.css')as the first entry in the classic preset'scustomCssarray, with the site's ownsrc/css/custom.csslayered after it. The package supplies the design-token baseline and dark-theme Infima overrides; everything site-specific (primary color pulled from FreeMoCap.org's palette, navbar dropdown styling, version-badge placement) lives in the local layer. One known gap patched locally: the package defines--ifm-background-coloronly for[data-theme='dark'](#0a0818) and never for:root, so light mode rendered a transparent page background until this site added an explicit white value. - A webpack compatibility shim. The config carries a
skellydocsWebpackFixesplugin that setsresolve.fullySpecified: falsefor.m?jsfiles and ignores.docusaurus/in watch options. It exists because the package ships unbundled ESM output (tsup/esbuild strips.jsextensions from relative imports) while webpack 5 enforces full extensions on ESM. Every SkellyDocs-based site repeats this plugin; the CLI scaffolds it into new ones. - Components, indirectly. This site's own pages do not import the package's React components. The homepage is fully custom. But the aggregated sub-repo docs do: the fetched SkellyCam docs (mounted at
/skellycam/) importAiGeneratedBanner,Tip,CoreFeatureHeader, andLinkedIssuesthroughout, so those components ship in this site's bundle whether or not its hand-written pages use them.