Skip to content

docs: README visibility overhaul — problem-first hook, dashboard hero, MCP quickstart - #77

Open
TheAmericanMaker wants to merge 1 commit into
mainfrom
docs/visibility-readme-overhaul
Open

docs: README visibility overhaul — problem-first hook, dashboard hero, MCP quickstart#77
TheAmericanMaker wants to merge 1 commit into
mainfrom
docs/visibility-readme-overhaul

Conversation

@TheAmericanMaker

Copy link
Copy Markdown
Member

What

The product has real adoption (~1,800 npm installs/month) but almost no social signal (1 GitHub star). People install and leave without starring or talking about it. This PR closes the discoverability + conversion gap — it is a marketing problem, not a quality problem.

Changes

  • README opening rewritten for the 5-second test: leads with the problem (understand an unfamiliar codebase + get a validated spec), drops "cartography" from line 1, names supported agents (Pi, Claude Code, Cursor, Codex, MCP) up front.
  • Dashboard hero screenshot added (docs/demo-dashboard-hero.png). Generated from a hand-authored demo workspace via the real writeDashboard() renderer — no LLM run needed. Build script: scripts/build-demo-dashboard.mjs (output gitignored except the hero PNG).
  • "Why CodeCartographer" section: filesystem-as-memory, validated phases, spec-not-chatlog output. The three things that differentiate from "just prompt the LLM to analyze the repo."
  • Star nudge near the top: "If CodeCartographer saves you a day of codebase archaeology, star the repo."
  • docs/mcp-quickstart.md: 30-second setup for Claude Code, Cursor, Codex, Claude Desktop, opencode. Linked prominently from the README install section.
  • docs/visibility-roadmap.md: documents what was done tonight + what still needs the user (real LLM run, case study, codecarto.dev, demo video, starter library). For later review.
  • .gitignore: demo workspace + non-hero screenshots gitignored as build artifacts.

Verification

  • Tests: 270/270 pass
  • Build: tsc clean
  • Doc-mention test: 6/6 pass (validates the new docs links)

Not in this PR (done separately / needs user)

  • GitHub repo topics updated via gh repo edit (already applied to the repo, not a commit): added codebase, ai-agent, context-engineering, code-understanding, spec-driven (was 7 topics, now 12).
  • Real LLM-backed analysis run + case study (needs user sign-off on token cost)
  • codecarto.dev homepage content (needs user to point at hosting)
  • Demo video (needs interactive Pi session)

See docs/visibility-roadmap.md for the full list of follow-ups.

…, Why section, MCP quickstart

- Rewrite README opening for the 5-second test: lead with the problem
  (understand an unfamiliar codebase + get a validated spec), drop
  'cartography' from line 1, name the supported agents up front.
- Add a real dashboard screenshot (docs/demo-dashboard-hero.png) as a
  hero image. Generated from a hand-authored demo workspace via the
  real writeDashboard() renderer — no LLM run needed. Build script:
  scripts/build-demo-dashboard.mjs (gitignored output).
- Add a 'Why CodeCartographer' section: filesystem-as-memory,
  validated phases, spec-not-chatlog output.
- Add a 'star if you use it' nudge to convert the existing install
  base into social signal.
- Add docs/mcp-quickstart.md — 30-second setup for Claude Code,
  Cursor, Codex, Claude Desktop, opencode. Linked prominently from
  the README install section.
- Add docs/visibility-roadmap.md for the user's later review
  (documents what was done tonight + what still needs the user).
- Gitignore the demo workspace + non-hero screenshots (build
  artifacts); commit only the hero PNG and the build script.
- GitHub repo topics updated (codebase, ai-agent, context-engineering,
  code-understanding, spec-driven) — done via gh, not in this commit.

Tests: 270/270 pass. Build: clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant