Improve PostHog usage auto-mapping and one-line install UX#134
Improve PostHog usage auto-mapping and one-line install UX#134abrichr wants to merge 26 commits into
Conversation
✅ Deploy Preview for cosmic-klepon-3c693c ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Update event classification to include events from openadapt-evals
standalone trainer (PRs #196-#222):
Runs: training_run, training_step_completed, rollout_collected,
checkpoint_saved, demo_execution
Demos: correction_captured, correction_stored
Fallback patterns updated to match training/rollout/checkpoint names.
Classification version bumped to 2026-03-29.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Packages not on PyPI (openadapt-agent, openadapt-blog, openadapt-console) were causing 404 errors and "package not found" console warnings. The discover-packages API already sets on_pypi: false for these. Now pypiStats.js and pypistatsHistory.js check this flag before fetching stats, eliminating the 404s and reducing rate limiting. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Closing as parked, not abandoned. Rationale: the homepage AdoptionSignals feature renders usage counts that are currently zero (the PR's own notes confirm 30d event volumes are 0), so shipping it now would display '0 demos / 0 runs' — anti-social-proof pre-launch. Usage metrics are a post-traction feature. The branch is 3.5 months stale and conflicts across 13 files the site rework has since churned, so reviving wholesale isn't worth it. The genuinely useful parts are being rebuilt fresh, focused, and privacy-conscious: (1) a true one-liner install, (2) lightweight launch-funnel instrumentation for INTERNAL measurement (Show HN → install → book), with no public zero-display. Revive the concept of on-site usage metrics when counts are real and it's actual social proof. |
1 participant
Summary
This PR upgrades homepage adoption signals and install UX with production-safe defaults.
1) Usage metrics from PostHog (server-side)
function_traceget_events.startedget_events.completedvisualize.startedvisualize.completed2) PostHog config ergonomics
POSTHOG_PROJECT_IDnow defaults to68185in API logic (still overridable by env)..env.examplefor required server-side keys.phc_project token misuse:phx_) is required for reads.3) Install UX
Runtime verification
npm run buildpasses./api/project-metricsreportssource=posthog_event_definitions0because PostHog event-definition 30d volumes for mapped events are currently zero.Notes
(30d)means rolling last 30 days.