Skip to content

add google analytics #215

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

Closed
wants to merge 1 commit into from
Closed

add google analytics #215

wants to merge 1 commit into from

Conversation

AucT
Copy link
Collaborator

@AucT AucT commented Feb 3, 2025

Summary by CodeRabbit

  • New Features
    • Integrated Google Analytics tracking to enhance website analytics.
    • Updated the site configuration and layout to seamlessly load analytics tracking for improved user interaction insights.

Copy link
Contributor

coderabbitai bot commented Feb 3, 2025

Walkthrough

The changes add Google Analytics integration across the project. A new [services] section is introduced in the configuration file with a nested [services.googleAnalytics] table that sets the tracking ID. Additionally, an extra line in the configuration file is removed. In parallel, the base layout now includes a partial call to load the Google Analytics snippet, and a new partial template generates the asynchronous GA tracking script dynamically if the configuration contains a valid ID.

Changes

File Change Summary
hugo.toml Added a new [services] section with a nested [services.googleAnalytics] table specifying ID = 'G-WDX8QHEBBR'; removed an extraneous trailing line.
themes/.../baseof.html and themes/.../google_analytics.html Introduced Google Analytics integration by including a new GA partial in the base layout and adding a partial template that conditionally loads the GA tracking script asynchronously.

Sequence Diagram(s)

sequenceDiagram
    participant B as Browser
    participant L as Base Layout
    participant GA as GA Partial
    participant GAS as GA Service

    B->>L: Request page
    L->>GA: Include GA partial before </head>
    GA->>GA: Check for GA ID in config
    alt GA ID exists
        GA->>GAS: Load GA tracking script asynchronously
        GAS-->>GA: Script loaded and initialized
    else No GA ID
        GA-->>L: Skip loading GA script
    end
    GA-->>L: Return GA tracking snippet
Loading

Poem

I'm a coding rabbit, hopping with delight,
Found a new GA path shining ever so bright.
With config tweaks and snippets that gleam,
Tracking journeys like a carrot-fueled dream.
Leaping through code, I celebrate the change with a smile!
🐇✨


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 950d606 and 61c5229.

📒 Files selected for processing (3)
  • hugo.toml (1 hunks)
  • themes/beaver/layouts/_default/baseof.html (1 hunks)
  • themes/beaver/layouts/partials/google_analytics.html (1 hunks)
🔇 Additional comments (3)
themes/beaver/layouts/partials/google_analytics.html (1)

1-11: Google Analytics Template Integration Looks Solid.
The partial template correctly checks for the presence of a Google Analytics ID in the site configuration and conditionally loads the Google Tag Manager (gtag.js) asynchronously, initializing the dataLayer and configuration appropriately.

themes/beaver/layouts/_default/baseof.html (1)

56-57: Well-Placed Inclusion of Analytics Partial.
The addition of {{ partial "google_analytics.html" }} just before the inline style block within the <head> section ensures that GA is loaded early. This placement is appropriate to capture page view events as soon as possible.

hugo.toml (1)

9-11: Google Analytics Configuration Setup is Correct.
The new [services] section with the nested [services.googleAnalytics] table and the ID = 'G-WDX8QHEBBR' entry is concise and aligns with Hugo’s configuration practices. Please ensure that the key case (i.e. GoogleAnalytics in the template vs. googleAnalytics in TOML) resolves as expected per Hugo’s config normalization.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@AucT AucT requested a review from pftg February 3, 2025 18:21
@pftg
Copy link
Member

pftg commented Feb 4, 2025

This should be done for elital, sorry if I missed that

@pftg pftg closed this Feb 6, 2025
@pftg pftg deleted the add-ga branch February 6, 2025 15:15
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