gate locale behind functional consent

dist/globals/SiteSettings/fields/general.d.js

@@ -1,6 +0,0 @@
-/**
- * General site identity fields.
- * Consumed by SEO/OG (siteName, defaultShareImage) and frontend (logo).
- */ export { };
-
-//# sourceMappingURL=general.d.js.map

dist/globals/SiteSettings/fields/general.d.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["general.d.ts"],"sourcesContent":["import type { Field } from 'payload';\n/**\n * General site identity fields.\n * Consumed by SEO/OG (siteName, defaultShareImage) and frontend (logo).\n */\nexport declare const generalFields: Field[];\n"],"names":[],"mappings":"AACA;;;CAGC,GACD,WAA4C"}

dist/globals/SiteSettings/fields/navigation.d.js

@@ -1,3 +0,0 @@
-export { };
-
-//# sourceMappingURL=navigation.d.js.map

dist/globals/SiteSettings/fields/navigation.d.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["navigation.d.ts"],"sourcesContent":["export {};\n"],"names":[],"mappings":"AAAA,WAAU"}

dist/globals/SiteSettings/fields/theme.d.js

@@ -1,9 +0,0 @@
-/**
- * Theme behavior configuration.
- *
- * These are decisions, not visuals — the plugin stores them, the client
- * template reads them and decides whether to render a toggle and which
- * mode to start in. Appearance itself stays in the template.
- */ export { };
-
-//# sourceMappingURL=theme.d.js.map

dist/globals/SiteSettings/fields/theme.d.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["theme.d.ts"],"sourcesContent":["import type { Field } from 'payload';\n/**\n * Theme behavior configuration.\n *\n * These are decisions, not visuals — the plugin stores them, the client\n * template reads them and decides whether to render a toggle and which\n * mode to start in. Appearance itself stays in the template.\n */\nexport declare const themeFields: Field[];\n"],"names":[],"mappings":"AACA;;;;;;CAMC,GACD,WAA0C"}

dist/globals/SiteSettings/index.d.js

@@ -1,3 +0,0 @@
-export { };
-
-//# sourceMappingURL=index.d.js.map

dist/globals/SiteSettings/index.d.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["index.d.ts"],"sourcesContent":["import type { Field, GlobalConfig } from 'payload';\ntype BuildSiteSettingsArgs = {\n    /** Extra fields injected by the client project */\n    additionalFields?: Field[];\n    /**\n     * Fields for the \"System Pages\" tab — page assignments by role (homepage,\n     * privacy policy, collection archives). Assembled by the caller, which is the\n     * only place that knows which modules are enabled. The tab is omitted when\n     * this is empty.\n     */\n    systemPageFields?: Field[];\n};\n/**\n * Builds the SiteSettings global.\n *\n * Composes tabs out of field groups; it deliberately doesn't know where those\n * groups come from. Earlier it imported the pages and content modules directly,\n * which meant a global — a presentation-layer concern — had an opinion about\n * blogs. Now the plugin's composition root passes fields in, and adding a new\n * kind of page assignment needs no change here.\n *\n * Uses unnamed tabs — data stays flat (siteSettings.siteName, not\n * siteSettings.general.siteName). Client-provided fields land in their own\n * \"Custom\" tab so core data paths never shift.\n */\nexport declare function buildSiteSettings({ additionalFields, systemPageFields, }?: BuildSiteSettingsArgs): GlobalConfig;\nexport {};\n"],"names":[],"mappings":"AA0BA,WAAU"}