Analytics docs refresh #798
Open
+99
−19
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will refresh our analytics docs for admins. This centralizes all customer-facing analytics content into a single, top-level product section, and describes the future structure of our analytics (cloud vs. self-hosted).
While these docs still have a lot of blanks, and don't perfectly reflect the current reality (e.g. "Cody Analytics" hasn't become "Sourcegraph Analytics" yet; the self-hosted analytics product isn't available in GA yet; etc.), it's a better setup than what we currently have and is a format we can build on in the coming months.
Please call out any gaps or issues you see here.
I use screenshots from the current cody analytics product and from the offsite grafana product
Pull Request approval
You will need to get your PR approved by at least one member of the Sourcegraph team. For reviews of docs formatting, styles, and component usage, please tag the docs team via the #docs Slack channel.