mirror of https://github.com/runbear-io/beardrive.git synced 2026-08-25 08:08:08 +02:00

Files

T

19da7dc890 site: move the landing page to the cloud module (#37 )

The landing page sells BearDrive Cloud, so it now lives in the private
cloud module (web/landing, served by the hub at / for signed-out visitors)
instead of this repo. A self-hosted hub should never serve "Start free"
CTAs pointing at our managed service, and marketing for the paid product
doesn't belong in the AGPL tree.

Rebuilt there as an Astro site on the webapp's own design tokens, so the
landing and the app stop drifting apart visually.

Doc pointers updated to the new location.


Claude-Session: https://claude.ai/code/session_01RA5pQH92cxk5SfiYJeTUjK

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-19 16:58:45 -07:00

4.1 KiB

Raw Blame History

GTM handoff — actions only Snow can take

Everything the GTM loop cannot do from inside the repo, prioritized. Draft copy is ready to paste; adjust voice as you like.

P0 — do before anything else (minutes each)

Enable GitHub Discussions on runbear-io/beardrive (Settings → Features). Then add categories: Announcements, Q&A, Ideas, Show & tell. CONTRIBUTING.md already links "where to ask" there.
Set GitHub repo topics: ai-agents, claude-code, file-sync, sync, agent-memory, self-hosted, golang, agpl. (Repo → About → gear.)
Set the repo social-preview image (Settings → Social preview): use docs/assets/insights.png for now — it's the most striking frame; replace with a branded card later.
Repo About blurb → paste:

The open-source Google Drive for AI agents: one folder your team and their agents share — synced in seconds, every change attributed, with read analytics. Self-host in one Go binary. Website field: https://beardrive.ai.
Verify the install path from a clean machine (the #1 CTA must not 404 on launch day): brew install runbear-io/tap/beardrive && bdrive version, and go install github.com/runbear-io/beardrive/cmd/bdrive@latest. If the tap is stale, cut a fresh goreleaser release first.
Verify the full first run, not just the binary: on a clean machine, bdrive login <a working hub> && bdrive init && edit a file && bdrive log must succeed end to end. Until BearDrive Cloud is live, every try-path (README, website, launch posts) must route people to self-hosting — bare bdrive login defaults to beardrive.ai and MUST NOT be advertised until that hub actually accepts logins. Gate any launch on this check.
Seed 3–5 good first issue / help wanted issues from ROADMAP.md (more agent platforms in bdrive hooks install; per-path access scopes design discussion; demo assets; docs gaps) — CONTRIBUTING.md promises curated starter issues; make it true.

P1 — demo assets (an hour)

Record a 45–60s demo GIF/video for the README hero and any launch post. Script (uses two terminals + a browser):
- T1: bdrive init --name demo --yes in a folder with a few notes → show bdrive status (daemon running).
- T1: have Claude Code write wiki/findings.md (or just edit it) → within seconds…
- T2 (second machine/dir): the file appears; bdrive log -n 3 shows the change attributed to the agent session.
- Browser: the hub's History view for that file, then Insights.
- T1: bdrive share wiki/findings.md → open the public URL. Tools: vhs (charmbracelet) or QuickTime + gifski. Put the result at docs/assets/demo.gif and add it above the fold in README.
Verify beardrive.ai serves the updated landing page (now cloud/web/landing/, served by the hub itself at / for signed-out visitors) after the next deploy.

P2 — when you're ready to be seen (launch window)

Show HN post — full drafts in launch-plan.md: title, body, and the first-comment founder note. Post from your account; be present for the first 3 hours to answer everything.
Product Hunt — drafts in launch-plan.md. Schedule after HN, not the same day. Before PH: replace the mailto waitlist on the site with a real form (any hosted waitlist works) — email-composer friction kills launch-day conversion.
Claude Code plugin discoverability — submit/announce the marketplace entry wherever Anthropic surfaces community plugins (Discord, awesome-lists PRs from your account).

P3 — measurement plumbing (see metrics.md)

Turn on GitHub traffic watching: stars/clones/views are under Insights → Traffic; consider a weekly note of the numbers in Discussions → Announcements.
Homebrew install counts: brew info --analytics runbear-io/tap/beardrive (public analytics take ~30 days to appear).
Decide on hub-side opt-in telemetry (proposal in metrics.md — requires your explicit approval before any implementation; nothing is wired today).

4.1 KiB Raw Blame History Unescape Escape