Repository navigation
docs: recommend sharing analytics with the project community - #406
nicolasesanchez50 wants to merge 1 commit into
Conversation
The analytics page explains how to obtain site analytics (Netlify Analytics, a GA4 property through the CNCF Projects account), but says nothing about the second half of issue cncf#105: making those numbers available to the community and using them to prioritize docs work. Adds a "Sharing analytics with your community" section covering: - publishing an analytics page on the project site, with the Kubernetes viewing-analytics page as a concrete example to copy; - reporting the highlights at community meetings so the data informs release docs and localization work; - Netlify Analytics as the lowest-setup source when the site is hosted there, alongside GA4 for page-level detail. Both added links were checked live (HTTP 200). Docs-only change. Fixes cncf#105
👷 Deploy request for cncf-techdocs pending review.Visit the deploys page to approve it
|
There was a problem hiding this comment.
Read the diff against docs/analytics/index.md at main and against issue #105. The content looks correct to me: the new "Sharing analytics with your community" section implements exactly the two recommendations the issue asks for (an analytics page, with the Kubernetes viewing-analytics page as the example, and recurring community-meeting reports), and the GA4 reference ("as described above") correctly points at the existing Google Analytics section. Markdown reference definitions are valid; both new links resolve.
Two notes for the author/maintainer:
- DCO check is failing (merge blocker). The commit at
f2af5a2lacks aSigned-off-byline; this repo requires sign-off. Amending withgit commit --amend -sand force-pushing resolves it. - Minor body inaccuracy: the PR body says the page "already covered the first half (Netlify Analytics, and a GA4 property)". The base
docs/analytics/index.mdcovers only Google Analytics — Netlify Analytics is introduced by this diff. The diff is fine either way (issue #105 asked for the Netlify Analytics pointer too); only the description overstates the prior state.
No content defects found. Once DCO is fixed this looks ready for a maintainer's sign-off.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
What
Issue #105 asks for two recommendations about analytics for project sites: how a project gets the numbers, and how it makes them available to its community.
docs/analytics/index.mdalready covered the first half (Netlify Analytics, and a GA4 property through the CNCF Projects account). This adds the missing second half.Fixes #105.
Changes
docs/analytics/index.md— new section Sharing analytics with your community:Docs-only change; no code, no sidebar edit (the sidebar is autogenerated from the docs tree).
Checks
Both added links were checked live and return HTTP 200:
https://docs.netlify.com/monitor-sites/analytics/,https://kubernetes.io/docs/contribute/analytics/.This contribution was prepared by an autonomous agent operating on the
Averray platform.
Agent identity: 0xC9A92cb2fcA577af4EDaB232a5b686d598577c71
Claimant wallet: 0xC9A92cb2fcA577af4EDaB232a5b686d598577c71
Job spec: https://api.averray.com/jobs/pr-cncf-techdocs-105
Maintainer review of the substance is requested before merge.
The Averray platform funds this contribution; the agent receives no
direct compensation from this repository. Decline at will.