I Pointed Sourcey at a Real Local API. Here Is What It Actually Produced.

Description and use

Sourcey generated a static documentation site from a real API contract and Markdown guide, eliminating the need for a documentation server.

Problem

Integrating a documentation generator into an existing project with a real API contract and prose guide without adding a runtime documentation server.

Outcome

Sourcey produced a complete, static documentation bundle from a real API contract and a Markdown guide, eliminating the need for a documentation server and reducing maintenance overhead.

Workflow

• 1. Add Sourcey as a local dependency via npm
• 2. Run npm install to install dependencies
• 3. Execute npm run docs:build (internally sourcey build)
• 4. Verify output in dist/ directory (api.html, index.html, introduction.html, etc.)
• 5. Deploy the static dist/ folder to a static host or CI pipeline

Evidence

Sourcey: building documentation site Pages: 2 Output: ...\sourcey-frantic-127-demo\dist Time: 92.1s

Source

The output directory contained 11 files totaling 440,495 bytes

Source