CMS And Content

1. 1

   Edit client-side canvas state

   The editor manages block state, selection, history, recovery, and validation before submit.

   Relevant Product code

   • src/features/cms/ui/editor/page.tsx
   • src/features/cms/shared/editor/canvas/state.ts
   • src/features/cms/shared/editor/validation/validation.ts
2. 2

   Submit through server actions

   Editor actions validate payloads and delegate persistence to content-owned services.

   Relevant Product code

   • src/features/cms/server/documents/actions/editor.ts
   • src/features/cms/server/documents/services/editor-upsert.ts
3. 3

   Revalidate public routes

   Maintenance actions keep published content routes in sync with database changes.

   Relevant Product code

   • src/features/cms/server/documents/actions/maintenance.ts
4. 4

   Render public content

   Public queries and renderers map stored content kinds into blog, FAQ, changelog, case study, page, legal, and team surfaces.

   Relevant Product code

   • src/features/cms/server/documents/queries/public.ts
   • src/features/cms/ui/public/articles/content-renderer.tsx
   • src/features/cms/shared/documents/kinds.ts

Use this example as a starting point, then adapt it to your product's rules and configuration.

Validation errors are projected into stable field labels for the editor UI.

export function buildValidationItems(
  fieldErrors: Record<string, string | undefined> | null,
): ValidationItem[] {
  if (!fieldErrors) return [];
  return Object.entries(fieldErrors)
    .filter(([, message]) => Boolean(message))
    .map(([key, message]) => ({
      key,
      label: labelForField(key),
      message: message ?? "",
    }));
}