Skip to content
Ascend GTM Ops — Docs

Delete `docs/archive/docs-site-docusaurus/`

ADR-064 — Delete docs/archive/docs-site-docusaurus/

  • Status: Accepted
  • Date: 2026-05-20
  • Owner: Mishaal (founder) — implemented autonomously
  • Supersedes: none
  • Related: ADR-058 (vendor gap-fill policy), .claude/memory/2026-05-09.md (historical archive note)

Context

docs/archive/docs-site-docusaurus/ is an archived scaffold of a never-shipped Docusaurus docs site. It was retired in April 2026 after PR #424 mistakenly treated the live Mintlify docs config as Docusaurus. The directory has not been built, deployed, or referenced from production code since.

Its package.json still pins Docusaurus v2 plus a tail of transitive deps that GitHub Dependabot now flags. Live audit (2026-05-20):

  • archived dir: 24 vulnerabilities (20 high, 4 moderate)
  • repo root: 7 vulnerabilities (1 high, 6 moderate)

The 24 high/moderate alerts in the archive directory account for ~50% of the remaining Dependabot signal across the repo, none of which is reachable from any shipped code path. The only inbound reference in the repo is .claude/memory/2026-05-09.md, a historical note explaining why the dir was archived in the first place — it does not require the files to exist.

Decision

Delete docs/archive/docs-site-docusaurus/ from the working tree. Keep the memory note intact (git history remains the audit trail). Do not migrate dependencies; do not run a semver-major bump on Docusaurus; do not revive the site.

Consequences

Positive

  • Eliminates 24 Dependabot alerts (20 high, 4 moderate) in a single commit — no risk, no semver churn.
  • Reduces repo size by ~1.1 MB and 59 files.
  • Removes a permanent source of false-positive supply-chain noise that competes with real vulns for triage attention.

Negative / risks

  • If we ever decide to revive a Docusaurus-based docs site, the scaffold is gone. Mitigation: full content is preserved in git history; git log --diff-filter=D --summary -- docs/archive/docs-site-docusaurus/ resurrects any file. Realistically Mintlify is the canon and Docusaurus revival is not on any roadmap.

Reversal trigger

Decision to launch a Docusaurus-based docs site. In that case, recover via git checkout <pre-delete-sha> -- docs/archive/docs-site-docusaurus/ and run npm audit fix against current Docusaurus v3 before re-committing.

Implementation

Single commit on claude/drop-archived-docusaurus-2026-05-20:

git rm -r docs/archive/docs-site-docusaurus/

Verification: npm audit --json | jq '.metadata.vulnerabilities' shows the 24-CVE drop post-merge.