Repository navigation
feat(docs): start independent TypeScript documentation engine without VitePress runtime - #71
Merged
Merged
Conversation
…data, callouts, code highlighting and interactive placeholders
…ayout, SEO, sitemap, search index, styles and JS
…with accessible dark mode and bilingual navigation
…me, mobile navigation and release-aware CLI widget
… any website framework or bundler
…n/YAML parsing libraries
… anchors, SEO, local search and interactive widgets
…first client transpilation error
…-free browser transpilation
…eme, mobile and axe WCAG scans
…ongside existing production browser suite
…d return keyboard focus
…first 2500 characters
…wn tables keyboard-scrollable
…oduction migration gates
…ate responsive wrapper
…representing production
…RL safety contract
This was referenced Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the Phase 1 implementation milestone of #70 (does not close the full migration issue).
Introduces a self-owned docs engine
scripts/scarp-site/TypeScript generator parses the existing Markdown/YAML pages using focused data parser libraries, not VitePress/Vue as site renderer.scarp:buildandscarp:testcommands with 138-route/static/Unicode/XSS/release-parity assertions, and adds these to PR CI.Safety / non-goals of this PR
This is a shadow build only: generated output is
artifacts/scarp-engine-preview/scarp-docs/and excluded from Git. VitePress is still used by the live Pages workflow, offline archive and older tests until the custom site passes a separate real-browser parity and production migration gate. No stable release and no compiler semantic changes.Track the full VitePress removal, deployed-site switch and cleanup under #70. All existing compiler-tagged conformance jobs must stay green.