Repository navigation
docs(website): document the Cloudflare Web Analytics go-live steps - #918
Merged
Merged
Conversation
) Name the hostname the Web Analytics site is registered for (docs.donkey-kit.dev), where the site token comes from, and that the beacon only goes live once the beacon code has reached main, the sole published branch. Add the devtools check that closes #692's last acceptance criterion. Refs #916 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #916 (not
Closes: merging todevelopdoes not make the beacon live; #916 closes after thedevelop→mainpromotion and a live check).Summary
website/README.md: registerdocs.donkey-kit.devas a Web Analytics site using the manual JS snippet, copy the token fromdata-cf-beaconinto theCF_WEB_ANALYTICS_TOKENvariable, and note that the beacon only goes live once the beacon code has reachedmain, the only branch that gets published.beacon.min.jsloads, it reports tocloudflareinsights.com/cdn-cgi/rum, no console or CSP errors). That check was the last open acceptance criterion on Add production-only Cloudflare Web Analytics beacon to the docs site #692.developalready has the beacon gate, layout wiring, and workflow env from feat(website): load Cloudflare Web Analytics beacon on production docs (#692) #695.Test plan
npm testinwebsite/: 6/6 pass.npm run buildwith a 32-hexNEXT_PUBLIC_CF_WEB_ANALYTICS_TOKEN: the beacon renders onout/index.htmlandout/quickstart.html.ruff check .clean;lint-imports5 kept, 0 broken.pytest/mypy: not cleanly verified locally. The borrowed venv imports the main checkout'ssrc/, not this branch's, so 2 crewai retry tests failed, and mypy stopped on an error inside numpy's own stubs. The diff is README-only; CI on this PR is the authoritative check.Post-deploy steps
CF_WEB_ANALYTICS_TOKENrepository variable: already set (2026-10-02).develop→main; the first docs deploy after that publishes the beacon.https://docs.donkey-kit.dev, run the devtools check above, then close Enable the Cloudflare Web Analytics beacon on docs.donkey-kit.dev #916 and comment on Donkey-Development-Kit/donkey-development-kit-metrics#21.🤖 Generated with Claude Code