Idea: track clicks on "Improve this document" links
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- analytics, documentation
Research direction
Start by locating the shared article template or component that renders the “Improve this document” links, then review the existing Google Analytics setup. Add click tracking that records the page being viewed, and verify that clicks produce distinguishable per-page events in analytics.
Written by the indexing model from the issue text.
Description
An idea I wanted to write up before I lose it.
We have a link on all our articles to improve it. It goes to GitHub where someone can edit the file.
I'd like to track the number of times people click on that link, so that we get a sense of where people might be confused, even if they don't show us that feedback. We should be able to see this by page.
Since we're using google analytics, we should be able to wire up an event to fire when the link is clicked. I'll need to look into how to do it.
- Dominant language
- Dockerfile
- Stars
- 601
- Forks
- 158
- Avg merge
- 15h 46m
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nunit/docs
-
type:newpage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:framework
Difficulty 4/5 3-5 days Newbie friendliness 40/100
Maintainers usually reply within 1 day
-
Document F# EqualToOpenarea:framework
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
area:framework
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nunit/docs#1045 · 6 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PedestrianDynamics/pyFDS-Evac#228 ·
Maintainers usually reply within 1 day