-
Notifications
You must be signed in to change notification settings - Fork 200
Add support for embedding of analytics pixels on package pages #1042
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Building with GHC 9.x needs code rearrangements (due to TH).
9ac62d3
to
4c083dd
Compare
@andreasabel Any chance you can have another look? |
4c083dd
to
a1b3f12
Compare
a1b3f12
to
42fcc93
Compare
Any chance for another round of reviews, @gbaz? |
It looks good. I plan to give it a final review and merge before the next redeploy. Just been a bit slammed by other responsibilities! |
I merged in preperation for a redeploy, but noticed in testing that the list of pixels already created did not show up properly in the package page. (It does show up in the page that lists all pixels for all packages for a user). So I'm going to comment out links to this functionality for now in the release. A patch fixing that up would be welcome. |
Summary
This PR adds support for package maintainers to attach analytics pixels to one or more of their packages in order to better understand the web traffic to their package pages on Hackage. Specifying an analytics pixel URL will result in Hackage automatically embedding the provided URL in an image tag on the main package page.
Context
This PR comes from a previous discussion that @aviaviavi, @gbaz, and the hackage-admin email group. The original suggestion for the direction in this PR came @davean, in discussion with the Haskell Foundation regarding approaches for introducing more analytical tools for maintainers within Hackage.
What not in this PR
Support for analytics pixels to be embedded in generated Haddock documentation is a natural next step and can be included in a future PR.