Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs analytics? #360

Open
mishaone opened this issue May 15, 2018 · 4 comments
Open

docs analytics? #360

mishaone opened this issue May 15, 2018 · 4 comments
Assignees
Labels
help wanted Please, pick me up if you have time. SEV4 Low priority. task New content or other non-bug work. web Presentation on docs.openshift.io.

Comments

@mishaone
Copy link
Contributor

I wondered if it would be possible to set up some analytics for our docs so that we can get an idea about things like:

  • Where are users for our docs coming from?
  • What links are they clicking most i.e. what is the most useful content at the moment, link it to features in development to gauge what would be useful to document next.
  • What amount of time do they spend on various docs/modules. Lower times may suggest they did not find them useful/did not find what they were looking for while longer times suggest they used them.
@mishaone mishaone added help wanted Please, pick me up if you have time. task New content or other non-bug work. web Presentation on docs.openshift.io. labels May 15, 2018
@rkratky
Copy link
Collaborator

rkratky commented May 25, 2018

@joshuawilson, @maxandersen - as briefly discussed during the Program call, could you please advise how to go about this?

@maxandersen
Copy link
Collaborator

my notes stated @qodfathr said he had some ideas on how to use the adobe analytics in place rather than woopra/segment;
my proposal would have been to just add google analytics tracing - thats known to work for docs.

@mishaone
Copy link
Contributor Author

@rkratky are you comfortable taking ownership of this, whether it's to follow up on the analytics at a later date or close it if unnecessary?

@mishaone mishaone added the SEV4 Low priority. label Jun 12, 2018
@mishaone
Copy link
Contributor Author

I'll assign this to @rkratky since he's currently looking into this, to ensure all issues have an owner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Please, pick me up if you have time. SEV4 Low priority. task New content or other non-bug work. web Presentation on docs.openshift.io.
Projects
None yet
Development

No branches or pull requests

3 participants