VitePress docs monitoring

Draft. This outline will be expanded with verified, platform-specific detail.

How VitePress sites typically break

• The sidebar config in .vitepress/config typically decides which pages are reachable, so pages left out of it can become orphans.
• Heading anchors are generated from heading text; check the VitePress docs for how custom anchor ids are configured on your version.
• cleanUrls toggles /page vs /page.html and needs matching server configuration.

What the VitePress build catches, and what it misses

• Builds fail on dead internal links by default; ignoreDeadLinks relaxes this.
• The build misses external links, anchors on other sites, sitemap drift and orphaned pages.

Setting up redirects on VitePress

• Redirects live at the host level (vercel.json, Netlify _redirects); VitePress rewrites map source directories to URLs ('source/:page': 'destination/:page') but are not HTTP redirects.

How PathIntact monitors a VitePress site

• PathIntact detects VitePress via the VitePress generator meta tag and VP class names, reads the site statically, and offers a Vercel redirect snippet by default.