Conversation
|
@nrichers Can I get access to heap.io so I can see some data? 😅 |
Right — that sort of would be required to make sense of this PR, wouldn't it? Invited you just now, check your email. |
|
@gtagle since you mentioned you're looking at Heap again — FYI, this PR will use the same project as our production Platform UI, based on convos I had with Mehdi & Andres, and what I found in the Heap documentation. Nothing you need to do, mainly just an FYI. |
validbeck
left a comment
There was a problem hiding this comment.
I see the changes in _quarto.yml & heap.html, and see the script in the <head> on:
- Regular articles
- .
ipynb - Test descriptions
🎉
|
@validbeck @noosheenv I've added some restrictions to our Makefile for deploying the docs-demo site: you now need to be on the docs-demo branch to deploy. As discussed, the reason for this change is to avoid sending tracking info into our The docs-demo site uses the |
Internal Notes for Reviewers
This PR adds heap.io code to track how our docs are performing:
_quarto.yml— newinclude-in-headerparameter that referencesheap-production.htmlheap-production.html— the script include from heap.io for theproductionprojectMakefile— now prevents deploying the docs-demo site unless you are on thedocs-demobranch with its own development project trackingIn the HTML output, these changes show up inside of
<head>as expected:More background info in sc-5291.
External Release Notes