feat: add GDPR cookie consent banner #1216
Open
Conversation
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
Add a GDPR-compliant cookie consent banner that gates analytics (Google
Analytics) and functional cookies (comments) until user consent is given.
Features:
- Theme-consistent styling using CSS variables (light/dark mode)
- Settings panel with category toggles (necessary, analytics, functional)
- Consent stored in cookie for 365 days
- Google Analytics only loads after analytics consent
- Comments only load after functional consent
- Translations for all 32 supported languages
- Accessible with proper ARIA attributes and focus management
Configuration in hugo.yaml:
params:
cookies:
enabled: true
categories:
analytics: true
functional: true
When cookies.enabled is false, scripts load normally without consent gating.
Closes CaiJimmy#412
Contributor
Author
|
I took note of the previous PR that was attempted with Cookie Consent, and you mentiond that it "wasn't fitting into the style". This should match similar styling as much as possible. Some demos of it below (without having to visit the netlify site, you still can 😄 ) Banner (Dark Theme)
Banner (Light Theme)
Preferences (Dark Theme)
Preferences (Light Theme)
Functional Cookies Disabled - Comments Section (Dark Theme)
Functional Cookies Disabled - Comments Section (Light Theme)
|
Move Google Analytics consent logic to avoid shadowing Hugo's internal `_internal/google_analytics.html` template. Changes: - Rename google_analytics.html → cookies/analytics.html - Update head.html to conditionally load: - cookies.enabled=true: cookies/analytics.html (consent-gated) - cookies.enabled=false: Hugo's _internal/google_analytics.html - Align cookies/analytics.html with Hugo's internal template: - Support Privacy.GoogleAnalytics.Disable setting - Support Privacy.GoogleAnalytics.RespectDoNotTrack setting - Add UA- prefix deprecation warning Note: Custom JS is required for consent-gated GA because Hugo templates render at build time, but consent happens at runtime. We cannot call Hugo's internal template after the user grants consent - we must dynamically inject the GA script via JavaScript.
delize
force-pushed
the
GDPR-cookie-consent
branch
from
46d9727 to
d16f29c
Compare
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.
Add a GDPR-compliant cookie consent banner that gates analytics (Google Analytics) and functional cookies (comments) until user consent is given.
Features:
Configuration in hugo.yaml:
params: cookies: enabled: true categories: analytics: true functional: true
When cookies.enabled is false, scripts load normally without consent gating.
Closes #412