forked from molecule-ai/molecule-core
These files have been in public monorepo docs/ since the open-source restructure on 2026-04-18, but are operational (outreach targets, analytics tracking IDs, staged unpublished social copy) or strategic (launch plans, SEO briefs, keyword targets, competitive research). Per the internal documentation policy (2026-04-22), they belong in the private internal repo. Pair PR: internal#27 receives the files. Removed: - docs/marketing/campaigns/* — 6 campaign packs with outreach + analytics - docs/marketing/plans/phase-30-launch-plan.md — draft launch plan - docs/marketing/briefs/* — 2 SEO content briefs - docs/marketing/seo/keywords.md — keyword strategy - docs/research/cognee-*.md — 2 architecture + isolation evals What stays public: - docs/marketing/blog/ — published blog posts - docs/marketing/devrel/demos/ — dev-facing demo scripts + video - docs/marketing/discord-adapter-day2/ — already-posted community copy No external references to update — cross-references among these files are now intact inside the internal repo; no public CLAUDE.md / README / PLAN / docs/README referenced the moved paths. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| adapters | ||
| adr | ||
| agent-runtime | ||
| api-protocol | ||
| architecture | ||
| assets/branding | ||
| blog | ||
| development | ||
| frontend | ||
| guides | ||
| incidents | ||
| infra | ||
| integrations | ||
| marketing | ||
| pages/api | ||
| plugins | ||
| tutorials | ||
| .gitignore | ||
| api-reference.md | ||
| glossary.md | ||
| index.md | ||
| quickstart.md | ||
| README.md | ||
| workspace-runtime-package.md | ||
docs/
This directory serves two purposes:
- Markdown content — everything under
architecture/,agent-runtime/,api-protocol/,development/,frontend/,plugins/,product/, etc. This is what agents and humans read. - VitePress site —
.vitepress/config.ts,package.json,package-lock.json. These drive the rendered documentation site.
Local preview
cd docs
npm install
npm run dev # preview on http://localhost:5173
npm run build # static build to docs/.vitepress/dist/
Conventions
- New top-level docs must be linked from
PLAN.md,README.md, andCLAUDE.md— otherwise agents can't find them (see.claude/memoryfeedback_cross_reference_docs.md). edit-history/YYYY-MM-DD.mdis append-only log of significant changes; don't rewrite history.archive/holds one-shot analyses and retired docs — kept for context but not maintained.
Why site tooling lives here (not in docs-site/)
VitePress expects its config at <root>/.vitepress/config.ts where <root> is also the content directory. Splitting tooling into a sibling docs-site/ would require a non-trivial srcDir shim and break relative links in .vitepress/config.ts. Keeping both together is the pragmatic choice; this README is the tradeoff ledger.