fls-build-links

To build a static site from Markdown for local preview, you need to compile the documentation project into deterministic HTML files, serve the built site locally, and verify navigation and rendering. This process ensures the documentation is accessible and up-to-date.

Automate link-checking for Markdown documentation by running a verification workflow that scans the built static site to detect broken references. This automated link verification ensures all internal and external references in the documentation remain valid and accessible.

Validating YAML frontmatter and Markdown structure requires a deterministic execution process that checks for required frontmatter presence and enforces Markdown structure rules. This validation happens during the build phase to ensure safe, reliable static-site generation.

Yes, you can serve a built static site locally to test navigation and rendering. Local serving allows you to verify that the documentation site functions correctly and is accessible before deploying it to a production environment.

No, the documentation build process does not require external dependencies. It operates with zero dependencies, ensuring safe and deterministic execution while handling YAML frontmatter validation, Markdown structure checks, and automated link verification.