Polish: drop hero pill, simplify Paper label, soften cite copy + re-apply GA4#13
Merged
radinhamidi merged 2 commits intomainfrom Apr 30, 2026
Merged
Polish: drop hero pill, simplify Paper label, soften cite copy + re-apply GA4#13radinhamidi merged 2 commits intomainfrom
radinhamidi merged 2 commits intomainfrom
Conversation
New shared component @qg/shared/components/GoogleAnalytics.astro reads `PUBLIC_GA_MEASUREMENT_ID` at build time. Astro inlines PUBLIC_* env vars into the static output, so each Cloudflare Pages project sets its own ID via "Environment variables": querygym-site → PUBLIC_GA_MEASUREMENT_ID = G-XXXXXXXXXX querygym-leaderboard → PUBLIC_GA_MEASUREMENT_ID = G-YYYYYYYYYY Component renders nothing if the env var is unset — keeps `pnpm dev`, preview branches, and forks silent (no analytics traffic from dev or contributor environments). Wired into both layouts: - web/site/src/layouts/Default.astro - reproducibility/site/src/layouts/Default.astro The inline config script is built as a string and emitted via set:html so Astro doesn't try to parse JS function-body curly braces as JSX expressions. No consent banner. GA4's default IP anonymization applies; add a banner if EU traffic becomes a real concern. Verified locally: with env var set, gtag.js + config render in <head> on both sites; without it, zero googletagmanager references in the output. Stacked on top of #11 (chore/site-seo). Once #11 merges, this PR's diff will narrow to just the GA bits. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Three small copy edits informed by user review: - Drop the "Open source · WWW 2026 · SIGIR 2026 Reproducibility" pill from the homepage hero. Hero h1 now sits at the top of the block (removed mt-5). - Footer Project link "Paper (WWW 2026)" → "Paper". The venue is visible on the destination page; the parenthetical was clutter next to the other one-word labels. - Cite intro: "comparing against the SIGIR 2026 leaderboard numbers" → "referring to the SIGIR 2026 leaderboard numbers". Softer and broader; not all referrers are doing comparisons. Also re-applies the GA4 component (cherry-picked from cf46b56), which was orphaned when PR #12 merged into the now-deleted chore/site-seo branch instead of main. Sets us up for both GA4 and Cloudflare Web Analytics running side-by-side once you flip the CF toggle in the dashboard. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 tasks
radinhamidi
added a commit
that referenced
this pull request
Apr 30, 2026
Three pieces of user-requested polish: 1. Marketing nav: add Leaderboard alongside Dashboard, both with the linkout arrow icon and opening in the current tab. Drop the trailing "↗" from the old "Dashboard ↗" label since the icon now conveys it. 2. Leaderboard nav: keep the Toolkit link (re-added earlier), with the same linkout icon, current-tab. 3. Header component: add a `newTab` prop separate from `external`. `external` controls icon rendering only; `newTab` controls target/rel. Default behavior is current-tab — let users middle-click / cmd-click for a new tab when they want one. Also propagate same-tab to EcosystemMap cards (they were forcing _blank for any http link). Sitemap visibility: `sitemap-index.xml` is one level above the URLs (it just points at sitemap-0.xml — standard Sitemaps protocol). When visited directly it looks empty. Updated <link rel="sitemap"> to point at /sitemap-0.xml so anything inspecting the page lands on the populated file. robots.txt now lists both URLs (crawlers handle either form). Stacked on chore/copy-polish (PR #13). Once that merges, this PR's diff narrows to just these files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three copy edits + a recovery of the GA4 component that was orphaned during the PR #11/#12 merge sequence.
Copy edits
GA4 re-apply
PR #12 merged into `chore/site-seo` (its base) rather than `main`. When PR #11 merged into main, only the SEO commit landed — the GA component was orphaned. Cherry-picked `cf46b56` so GA4 is back. Cloudflare Web Analytics is enabled separately in the CF dashboard (no code), so both run side-by-side.
Operator follow-up (CF dashboard)
For each CF Pages project (`querygym-site`, `querygym-leaderboard`):
Test plan
🤖 Generated with Claude Code