NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
Docs is looking for docs-fp-o related metrics - list of pages that got the most of views and reads.
Describe the problem Docs team want to prioritize efforts on QuickDocs and other user documentation based on site metrics and performance by pages and repos that help Docs team work on top performing 20 to 50 pages.
Describe the solution Give Docs team access to analytics dashboard and help create site metrics report for self-serve analytics.
Please find a related thread here.
https://discussion.fedoraproject.org/t/project-quick-docs-improvement-progress-report-2023-01-04/45549/8
@kevin Do we have any analytics dashboard for docs.fp.o?
We do not. in the past we had some... awstats most recently, but it was dropped a while back.
We do have google stats (ie, what sites/pages people were most directed to by search requests). I think @mattdm has access to that. I don't know if thats 'good enough' here, or if we want to try and make something better.
We do have apache logs... so something that consumes them would be best.
Metadata Update from @kevin: - Issue tagged with: medium-gain, medium-trouble, ops
We do not. in the past we had some... awstats most recently, but it was dropped a while back. We do have google stats (ie, what sites/pages people were most directed to by search requests). I think @mattdm has access to that. I don't know if thats 'good enough' here, or if we want to try and make something better. We do have apache logs... so something that consumes them would be best.
Thanks, will check the Google analytics wth matt
https://discussion.fedoraproject.org/t/project-quick-docs-improvement-progress-report-2023-01-04/45549/12
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Just looked at the discussion thread, and it seems that mattdm has google analytics set up and is giving access where it is needed.
@hankuoffroad going to close this one as INVALID -- but feel free to reopen it if you need anything more from the infra team on this.
Metadata Update from @ryanlerch: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.