Handling Relative Paths, Internal Links, and Anchors
Markdown documents rarely exist in isolation. AxelBase simulates a virtual project structure to validate internal references without requiring a live web server.
Simulating the Virtual File Tree
Relative paths like ../images/logo.png or ./setup.md are resolved against a Base Directory you specify. This allows the tool to verify structural integrity as if it were running inside your terminal.
Logic Preview:
Virtual Base: /project/root
→ Resolved: /project/root/docs/setup.md
Cross-Document and Anchor Validation
The checker doesn't just look for files; it looks inside them for navigation markers. In-page anchors (e.g., #installation-steps) are validated by scanning the document for matching Heading IDs.
Anchor Awareness
Missing anchors appear as warnings with the exact line number of the linking text. This ensures your "Jump to Section" links never leave a reader stranded at the top of a page.
Simulating Deployment Environments
Working on a project for GitHub Pages or a custom domain? You can set a Virtual Base URL. This mimics how links will behave after deployment, ensuring your relative paths resolve correctly whether viewed locally or on the web.
| Link Type | Validation Method | Requirement |
|---|---|---|
| External URL | Network Request (Fetch) | Internet Connection |
| Relative Path | Logical Path Resolution | Base Directory Set |
| Internal Anchor | DOM ID Matching | Heading with ID |
Thank you for following this series—happy validating and keep your Markdown links trustworthy and private.