Skip to content

Cut the dashboard caveat down to a footnote - #249

Merged
mmcky merged 1 commit into
mainfrom
analytics/caveat-as-footnote
Aug 7, 2026
Merged

Cut the dashboard caveat down to a footnote#249
mmcky merged 1 commit into
mainfrom
analytics/caveat-as-footnote

Conversation

@mmcky

@mmcky mmcky commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Follow-up to #248, at @mmcky's suggestion.

The explanatory note that came with the sessions relabel sat above the charts and ran to two paragraphs. The substance is worth keeping — these are visits rather than people, and the total spans eight lecture series — but it does not need the top of the page, above the charts people arrive for.

This cuts it to a single line below the charts, in smaller muted type above a horizontal rule:

Sessions are visits rather than unique readers, summed across eight QuantEcon lecture series. Translation traffic is counted under the corresponding English series.

That keeps the caveat recorded next to the chart, which is what QuantEcon/website-dynamic#9 asked for, without leading with it.

Dropped from the longer version: the explanation of why sessions rather than users are reported — that user counts cannot be summed across properties because GA4 offers no cross-property deduplication. That reasoning is recorded in QuantEcon/website-dynamic#9 and will be covered in the pipeline documentation under QuantEcon/website-dynamic#16, so it is not lost, just not on the page.

No change to the data the page reads or renders — the field reads are untouched and verified identical.

Happy to remove the footnote entirely instead if you would rather have nothing there; I kept a minimal version because #9's "done when" asked for the caveat to be stated next to the chart rather than left implicit.

🤖 Generated with Claude Code

The explanatory note added alongside the sessions relabel took the top
of the page, above the charts people come for. The substance is worth
keeping -- these are visits rather than people, and the total spans
eight lecture series -- but it does not warrant two paragraphs of prime
position.

Reduced to a single line below the charts, in smaller muted type above a
rule. Keeps the caveat recorded next to the chart, which is what
QuantEcon/website-dynamic#9 asked for, without leading with it.

No change to the data the page reads or renders.
Copilot AI lite review requested due to automatic review settings August 7, 2026 06:12
@netlify

netlify Bot commented Aug 7, 2026

Copy link
Copy Markdown

Deploy Preview for grand-swan-ca5201 ready!

Name Link
🔨 Latest commit 2919bcb
🔍 Latest deploy log https://app.netlify.com/projects/grand-swan-ca5201/deploys/6a757764b324d50008242ae5
😎 Deploy Preview https://deploy-preview-249--grand-swan-ca5201.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mmcky
mmcky merged commit ca70e21 into main Aug 7, 2026
6 checks passed
@mmcky
mmcky deleted the analytics/caveat-as-footnote branch August 7, 2026 06:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the QuantEcon analytics dashboard page to keep the “sessions vs people” caveat recorded near the charts while reducing its visual prominence.

Changes:

  • Removes the multi-paragraph explanatory note previously shown above the charts.
  • Adds a single-line footnote placed below the charts.
  • Updates styling by replacing the old note styles with a new “footnote” style.

Comment on lines +50 to +55
.dashboard-footnote {
max-width: 800px;
margin: 0 auto 3rem auto;
color: #5a6472;
font-size: 0.95rem;
line-height: 1.6;
}

.dashboard-note p {
margin: 0 0 0.75rem 0;
}

.dashboard-note p:last-child {
margin-bottom: 0;
margin: 3rem auto 0 auto;
padding-top: 1rem;
border-top: 1px solid #e0e0e0;
color: #7a828d;
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants