CookiezyCookiezy
ProductPlatformsDocsPricingBlogContact
  1. Home/
  2. Docs/
  3. Hugo Adapter Setup

Documentation last updated May 29, 2026

Docs navigation

Overview

DocsDeveloper-first documentation for installing, configuring, and verifying Cookiezy across every supported adapter.Getting StartedCheck readiness, generate the right package, then ship the core flow.InstallationInstallation follows the same core pattern everywhere: generate the issued package, register the hostname, install the adapter, and validate runtime verification before launch.ConfigConfiguration keeps locale, policy, categories, layout, and licensing context in sync.

Reference

APIDeveloper-facing runtime methods, browser events, and verification-aware integration notes.

Adapters

Webflow Adapter SetupTechnical Webflow setup guide for Cookiezy: what you receive after purchase, where each file goes, and how to validate the runtime on a published Webflow site.Shopify Adapter SetupTechnical Shopify setup guide for Cookiezy: download Platform Core, deploy the theme app extension, expose the Theme Editor fields, and validate storefront consent behavior before publish.Wix Adapter SetupTechnical Wix setup guide for Cookiezy: install the private or unlisted Wix app, connect the correct Cookiezy account, publish the app-hosted runtime, and keep custom code only as a fallback.Hugo Adapter SetupTechnical Hugo setup guide for Cookiezy: generate the dedicated Hugo package, copy the issued config scaffold, align locale routes, and validate banner plus cookie audit behavior.Headless Adapter SetupTechnical headless setup guide for Cookiezy: boot the plain adapter, wire runtime verification, and validate the audit, settings, and restricted-mode recovery flow in custom frontends.WordPress Adapter SetupTechnical WordPress setup guide for Cookiezy: upload the plugin ZIP, configure licensing-aware settings, and validate shortcode-based settings and audit behavior.React Adapter SetupTechnical React setup guide for Cookiezy: load the plain adapter from the app shell, gate optional services with consent state, and validate SPA behavior.Next.js Adapter SetupTechnical Next.js setup guide for Cookiezy: load the plain adapter from the root layout, keep policy routing localized, and validate consent gating across App Router pages.Strapi Adapter SetupTechnical Strapi setup guide for Cookiezy: keep the runtime on the frontend, use Strapi as a configuration bridge, and map locale-aware policy URLs through the shared core model.DatoCMS Adapter SetupTechnical DatoCMS setup guide for Cookiezy: keep the visitor-facing runtime in the frontend app, use Platform Core for runtime assets, and use the standalone DatoCMS plugin only for editor-side configuration and generated frontend config preview.
Adapter versioningHugo Adapter Setup

Adapter and release status

Hugo remains a dedicated issued package lane with prefilled config values rather than a Platform Core subpath.

Current version

0.1.23

Delivery lane

Issued ZIP

Compatibility notes

Hugo remains a dedicated issued package lane with prefilled config values rather than a Platform Core subpath.

Key rollout changes

1. Use the dedicated `cookiezy-hugo-package.zip` artifact.

2. Copy partials, static assets, and example config into the Hugo project.

3. Keep locale routes and policy pages aligned before publish.

Overview

Hugo adapter: dedicated package rollout

Use this guide when you are shipping Cookiezy through the dedicated Hugo package rather than Platform Core. The package already carries the issued licensing values, example config, and static assets.

  • • Generate `cookiezy-hugo-package.zip` from Downloads.
  • • Copy the partials, static assets, and example config into the Hugo project.
  • • Keep locale routes and policy URLs aligned before publish.
  • • Register the production hostname in billing, then validate banner, settings reopen, and cookie audit behavior.
Step 1

Copy the issued package into the Hugo project

The dedicated Hugo artifact already contains the shared runtime assets, Hugo partials, and an example config scaffold with the issued site key and verification URLs.

Code snippet

Package: cookiezy-hugo-package.zip
Copy into project:
- layouts/partials/cookie-consent/
- static/js/
- static/css/
- examples/config/
Step 2

Align config, locale routes, and policy URLs

Open the example config scaffold and carry the issued values into your real Hugo config. If the site is multilingual, keep `defaultLocale`, `localeRoutes`, and per-locale policy URLs aligned before launch.

  • • Copy the issued `siteKey`, `verifyUrl`, and `billingUrl` exactly and do not wrap them in extra escaped quotes.
  • • Make sure each locale points to the correct cookie policy page path.
  • • Keep the same locale map between the banner runtime and the published Hugo routes.
Step 3

Validate the live Hugo site

After publish, test the visitor-facing runtime on the real hostname.

  • • Banner appears on first visit.
  • • Reject optional keeps optional integrations blocked.
  • • Accept all unlocks the categories you configured.
  • • Settings reopen works from the footer or policy page.
  • • Cookie audit renders on the policy page and stays aligned after consent changes.
  • • Runtime verification returns `allowed: true` for the registered hostname.
Cookiezy

Lightweight consent platform for modern websites.

Product

FeaturesPlatformsPricingDocsBlogContact

Legal

Cookie PolicyPrivacy PolicyTerms

Language

English
EnglishenSlovenščinaslHrvatskihrItalianoit

Privacy controls

© 2026 Cookiezy. All rights reserved.