init commit for iPAL-kit plugin

src/globals/SiteSettings/index.ts

@@ -1,40 +1,37 @@
 import type { Field, GlobalConfig } from 'payload'
 
-import type { ContentOption } from '../../modules/content/index.js'
-import type { PagesOption } from '../../modules/pages/index.js'
-
-import { buildArchiveFields } from '../../modules/content/index.js'
-import { buildSystemPagesFields } from '../../modules/pages/index.js'
 import { generalFields } from './fields/general.js'
 import { themeFields } from './fields/theme.js'
 
 type BuildSiteSettingsArgs = {
   /** Extra fields injected by the client project */
   additionalFields?: Field[]
-  /** Archive-page assignments for content collections — joins the same tab */
-  content?: ContentOption
-  /** System-page assignments — adds a "System Pages" tab when provided */
-  pages?: PagesOption
+  /**
+   * Fields for the "System Pages" tab — page assignments by role (homepage,
+   * privacy policy, collection archives). Assembled by the caller, which is the
+   * only place that knows which modules are enabled. The tab is omitted when
+   * this is empty.
+   */
+  systemPageFields?: Field[]
 }
 
 /**
  * Builds the SiteSettings global.
  *
+ * Composes tabs out of field groups; it deliberately doesn't know where those
+ * groups come from. Earlier it imported the pages and content modules directly,
+ * which meant a global — a presentation-layer concern — had an opinion about
+ * blogs. Now the plugin's composition root passes fields in, and adding a new
+ * kind of page assignment needs no change here.
+ *
  * Uses unnamed tabs — data stays flat (siteSettings.siteName, not
- * siteSettings.general.siteName). Client-provided fields land in their
- * own "Custom" tab so core data paths never shift.
+ * siteSettings.general.siteName). Client-provided fields land in their own
+ * "Custom" tab so core data paths never shift.
  */
 export function buildSiteSettings({
   additionalFields,
-  content,
-  pages,
+  systemPageFields,
 }: BuildSiteSettingsArgs = {}): GlobalConfig {
-  // Archive assignments sit with the system pages: both answer "which page
-  // plays this role", and both turn into URLs through the page's own slug.
-  const systemPageFields = [
-    ...(pages ? buildSystemPagesFields(pages) : []),
-    ...(content && pages ? buildArchiveFields(content, pages.slug) : []),
-  ]
   return {
     slug: 'site-settings',
     access: {
@@ -55,7 +52,9 @@ export function buildSiteSettings({
             fields: themeFields,
             label: 'Theme',
           },
-          ...(systemPageFields.length ? [{ fields: systemPageFields, label: 'System Pages' }] : []),
+          ...(systemPageFields?.length
+            ? [{ fields: systemPageFields, label: 'System Pages' }]
+            : []),
           ...(additionalFields?.length ? [{ fields: additionalFields, label: 'Custom' }] : []),
         ],
       },