* docs(marketing): add social copy for chrome-devtools-mcp and fly-deploy-anywhere campaigns Two campaign social copy packages: - chrome-devtools-mcp-seo: 5 X posts + 1 LinkedIn post + campaign notes P0 keywords: AI agent browser control, MCP browser automation, browser automation AI agents, MCP governance layer - fly-deploy-anywhere: 5 X posts + 1 LinkedIn post + campaign notes Primary hook: ADMIN_TOKEN rotation without downtime Coordination: chrome-devtools-mcp Day 1, fly-deploy-anywhere Day 3–5. Social Media Brand to publish pending Marketing Lead approval. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * marketing(audio): add audit trail observability TTS clip audio/audit-trail-observability.mp3: 734KB, 197 words (~74s at 160wpm). Script: two-layer audit observability — Canvas Audit Trail + org API key attribution. Companion post: docs PR #53 (2026-04-21-audit-trail-api-logs). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs(marketing): social copy campaigns + TTS audio - chrome-devtools-mcp-seo social copy (5 X posts + LinkedIn) - fly-deploy-anywhere social copy (5 X posts + LinkedIn) - TTS: chrome-devtools, phase30, audit-trail audio Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * marketing: add Chrome DevTools MCP backlinks outreach draft Community outreach templates for r/programming, r/MachineLearning, r/webdev, LinkedIn, MCP GitHub, HN. Priority target list and guidelines. Action 6 from Marketing Lead brief. --------- Co-authored-by: Molecule AI Content Marketer <content-marketer@agents.moleculesai.app> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: molecule-ai[bot] <276602405+molecule-ai[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| adapters | ||
| adr | ||
| agent-runtime | ||
| api-protocol | ||
| architecture | ||
| assets/branding | ||
| blog | ||
| development | ||
| frontend | ||
| guides | ||
| integrations | ||
| marketing | ||
| plugins | ||
| research | ||
| 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.