QuantEcon / QuantEcon/lecture-dp

Re-add Google Analytics with a real GA4 measurement ID (or confirm none needed)

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

maintenance question
Dominant language
TeX
Stars
0
Forks
0
Avg merge
1d 22h
Merged PRs (30d)
2

Description

PR #26 removed a non-functional Google Analytics placeholder (google_analytics_id: G-XXXXXXXXXX) from lectures/_config.yml. It was never a real measurement ID, so it collected no data — removing it just stops shipping a dead config value. This issue tracks the follow-up decision: re-add analytics with a real ID, or confirm the site intentionally runs without it.

@DrDrij — do you have a GA4 measurement ID for dp.quantecon.org (or should this site report into an existing org-wide property)? If analytics are wanted, please provide the G-XXXXXXXXXX ID and we'll re-add the block; if not, we can close this as "no analytics by design".

To re-enable, add this back under html_theme_options in lectures/_config.yml (it sat just below keywords:), with the placeholder swapped for the real ID:

      analytics:
        google_analytics_id: G-XXXXXXXXXX   # replace with the real GA4 measurement ID for dp.quantecon.org

Context: split out from the tooling refresh tracked in #22; the removal landed in #26.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in lectures/_config.yml under html_theme_options, near keywords and the removed analytics block. First confirm whether a real GA4 measurement ID or an existing organization-wide property should be used. Done means either restoring the block with the confirmed ID or documenting that analytics are intentionally disabled.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.