feat: add GDPR cookie consent banner by delize · Pull Request #1216 · CaiJimmy/hugo-theme-stack

delize · 2025-12-24T22:39:59Z

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 #412

delize · 2025-12-24T22:46:39Z

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)

AiratTop · 2026-01-27T20:07:34Z

Waiting for merge

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

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 · 2026-02-02T20:21:49Z

Have rebased on the v4 changes from the past week

CaiJimmy · 2026-02-02T20:32:54Z

Have rebased on the v4 changes from the past week

Thanks! Sorry but I can't give you an ETA for reviewing this pull request as it contains a lot of changes, and currently I'm a bit busy with academic stuffs.

Did you use an AI tool for this by the way? Sorry if I'm wrong.

delize · 2026-02-02T20:42:22Z

Hey,

No worries.

Yeah. Typescript & design is not something I am good at, I can easily diagnose and troubleshoot general issues or templating / html, but creating a whole display element for example - not something I am a pro at. If you would prefer to not PR merge it on that alone - I am perfectly okay with that. I did actually review the code being generated - not just yolo it away - and made several changes based on either bad ui, bad general issues, and ensuring 0 console errors/warnings for the code itself.

I will say, a lot of the changes are just appended languages based on the il8n and the cookie banner info.

… and will throw error

CaiJimmy · 2026-02-19T16:21:27Z

Thanks!

delize · 2026-02-19T17:00:48Z

No worries that was a lot more revisions than I was expecting 🙈

* refactor: create a generic `taxonomy` widget (CaiJimmy#1268) * refactor: introduce a generic taxonomy widget and refactor existing category and tag cloud widgets to use it. * feat: Implement optional title linking for taxonomy widgets and enable parameter customization for taxonomy partials. * refactor: remove fallback to taxonomy page title for widget display Because this field always exists. I think it's better to let user customize via widget params * Update layouts/_partials/widget/taxonomy.html * refactor: check for .Params.taxonomy existence before accessing * feat: add markdown alerts support (CaiJimmy#1221) * Markdown alerts * refactor(alert): move alert color to variable.scss and simplify the style * style: fix indent in render-blockquote * feat(alert): add customizable alert icons for different alert types * doc: add example usage of markdown alert --------- Co-authored-by: Jimmy Cai <jimmy@cai.im> * feat(i18n): add i18n support for Markdown alert (CaiJimmy#1269) * docs: add blockquote with custom alert title * feat: add alert types to i18n and update blockquote rendering * fix: wrong translation key * feat: add alert title translation for all supported languages Done by AI * feat: add GDPR cookie consent banner (CaiJimmy#1216) * feat: add GDPR cookie consent banner 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 * refactor: move consent-gated GA to cookies/analytics.html 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. * style: indent cookies/analytics.html * refactor: don't use default, put default configurations in params.toml * fix: don't use `description` as translation key because it's reserved and will throw error * fix: remove footer/components/custom-font.html call * fix: banner showSettings key * style: indent comments/include * Add missing article.alert translation back * style: format i18n toml files * style: indent head/head.html * style adjustment * style: add missing - * style: format demo/config/params.toml * style: remove redundant comments from cookies.scss * style: update box-shadow for cookie banner content --------- Co-authored-by: delize <4028612+delize@users.noreply.github.com> Co-authored-by: Jimmy Cai <jimmy@cai.im> * feat(list): ability to show article tags on homepage (CaiJimmy#1270) * feat(list): ability to show article tags on homepage closes CaiJimmy#880 * Disable showTags by default * refactor(sidebar): drop support for .Pre and remove old codes (CaiJimmy#1271) * refactor(sidebar): drop support for .Pre and remove old codes * Simplify * doc(demo): disable cookie consent * ci: update Hugo version to 0.156.0 --------- Co-authored-by: Jimmy <jimmy@cai.im> Co-authored-by: Bigstool <20697772+Bigstool@users.noreply.github.com> Co-authored-by: Andrew Doering <delize@users.noreply.github.com> Co-authored-by: delize <4028612+delize@users.noreply.github.com>

* feat: add GDPR cookie consent banner 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 * refactor: move consent-gated GA to cookies/analytics.html 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. * style: indent cookies/analytics.html * refactor: don't use default, put default configurations in params.toml * fix: don't use `description` as translation key because it's reserved and will throw error * fix: remove footer/components/custom-font.html call * fix: banner showSettings key * style: indent comments/include * Add missing article.alert translation back * style: format i18n toml files * style: indent head/head.html * style adjustment * style: add missing - * style: format demo/config/params.toml * style: remove redundant comments from cookies.scss * style: update box-shadow for cookie banner content --------- Co-authored-by: delize <4028612+delize@users.noreply.github.com> Co-authored-by: Jimmy Cai <jimmy@cai.im>

delize marked this pull request as draft December 24, 2025 22:58

delize marked this pull request as ready for review December 24, 2025 23:06

delize force-pushed the GDPR-cookie-consent branch from 46d9727 to d16f29c Compare December 24, 2025 23:14

delize added 2 commits February 2, 2026 21:20

delize force-pushed the GDPR-cookie-consent branch from d16f29c to 29e082b Compare February 2, 2026 20:21

delize and others added 15 commits February 17, 2026 19:34

Merge branch 'master' into GDPR-cookie-consent

af5b6b2

Merge branch 'master' into pr/delize/1216

f7ab0be

style: indent cookies/analytics.html

7bdb663

refactor: don't use default, put default configurations in params.toml

48629e2

fix: don't use description as translation key because it's reserved…

d3099db

… and will throw error

fix: remove footer/components/custom-font.html call

2d7d1d6

fix: banner showSettings key

5d43872

style: indent comments/include

ed5e404

Add missing article.alert translation back

03331ed

style: format i18n toml files

e289878

style: indent head/head.html

e10dc42

style adjustment

1684664

style: add missing -

42b6ca3

style: format demo/config/params.toml

548fa24

style: remove redundant comments from cookies.scss

bd1e436

CaiJimmy approved these changes Feb 19, 2026

View reviewed changes

style: update box-shadow for cookie banner content

17f823f

CaiJimmy requested a review from Copilot February 19, 2026 16:14

Copilot started reviewing on behalf of CaiJimmy February 19, 2026 16:14 View session

CaiJimmy merged commit 4ad88a3 into CaiJimmy:master Feb 19, 2026
5 of 6 checks passed

delize review requested due to automatic review settings March 23, 2026 20:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add GDPR cookie consent banner#1216

feat: add GDPR cookie consent banner#1216
CaiJimmy merged 18 commits into
CaiJimmy:masterfrom
delize:GDPR-cookie-consent

delize commented Dec 24, 2025

Uh oh!

delize commented Dec 24, 2025

Uh oh!

AiratTop commented Jan 27, 2026

Uh oh!

delize commented Feb 2, 2026

Uh oh!

CaiJimmy commented Feb 2, 2026

Uh oh!

delize commented Feb 2, 2026

Uh oh!

Uh oh!

CaiJimmy commented Feb 19, 2026

Uh oh!

delize commented Feb 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

delize commented Dec 24, 2025

Uh oh!

delize commented Dec 24, 2025

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)

Uh oh!

AiratTop commented Jan 27, 2026

Uh oh!

delize commented Feb 2, 2026

Uh oh!

CaiJimmy commented Feb 2, 2026

Uh oh!

delize commented Feb 2, 2026

Uh oh!

Uh oh!

CaiJimmy commented Feb 19, 2026

Uh oh!

delize commented Feb 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants