Timothée Mazzucotelli
db4f8ef5dc
This commit fixes validation reporting false unresolved-reference errors for Markdown links that are successfully resolved by autorefs. Validation now runs after pages render, so it uses the autorefs results from the current build state and emits one complete issue report for that state. **Validation implementation summary:** - Page rendering now returns the identifiers that autorefs resolved, alongside rendered output. - Validation combines those resolutions with the source-page references and anchors; a reference resolved by autorefs is no longer reported as unresolved. - The workflow tracks a generation for page content and navigation, so it waits for matching render results from every page before creating issues. This prevents validation from using stale render data or printing duplicate reports during incremental updates. - Reference collection now follows the configured documentation directory, and tests cover reporting after rendering and a subsequent clean rebuild. Signed-off-by: Timothée Mazzucotelli <dev@pawamoy.fr>
A modern static site generator built by the creators of Material for MkDocs
Home · Get started · Compatibility · Roadmap · Newsletter · Zensical Spark
Write your documentation in Markdown and create a professional static site for your Open Source or commercial project in minutes – searchable, customizable, more than 60 languages, for all devices.
Visit our documentation at zensical.org/docs/.
Zensical Spark
Zensical Spark is our offering for professionals and organizations using Zensical commercially. It lets us provide best-in-class support, keep the project sustainable, and Zensical free for everyone.
Zensical Spark may be a great fit if you:
- Need help migrating a complex MkDocs project to Zensical
- Want to ensure Zensical meets all your requirements – see how we work
- Want direct support from the core team, including 1:1 sessions
For the full list of benefits, see our subscription tiers.