# Webflow CMS Publishing

## Objective

Push app content into Webflow CMS collections and publish it to the right site.

A one-way sync that creates and updates Webflow CMS items from app records and triggers site publishing.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Let an administrator connect a site and choose the target collection, then store the resolved collection and field identifiers rather than their display names, because designers rename things and the sync must survive it.
2. Build an explicit mapping between app fields and collection fields, held in configuration the operator can see and change, and refuse to sync a record whose mapping references a field that no longer exists in the fetched schema.
3. Keep a persistent link between each app record and the item it created, so a second sync updates the existing item instead of creating a duplicate every time the record is saved.
4. Treat publishing as a separate step from writing. Write the item, confirm it, then request the site publish, and surface the publish outcome to the operator because a written item that was never published is invisible to visitors.
5. Do not send a field the app has no value for. Writing an empty string over a description a designer wrote in Webflow destroys work the app did not create and cannot restore.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- Collection and field identifiers are the only stable reference. Matching by display name means the first rename in the designer silently redirects content into the wrong field or fails outright.
- Items exist in draft, archived, and published states, and the app must decide which state it writes and whether it is permitted to move an item out of a state a human deliberately set.
- Blank or missing app values must be skipped rather than written. A partial record in the app must not blank out designer-managed copy, images, or SEO fields on the live site.
- Collections have item ceilings and the API has request ceilings. Batch writes, back off on rate limit responses, and stop cleanly with a clear message when the plan's item limit is reached rather than retrying forever.
- A renamed collection, a changed schema, or a failed site publish must leave the app's link records intact and the sync paused with a readable error, not half-applied across a hundred records.
- Reference and multi-reference fields point at items in other collections. Those targets must be resolved and confirmed to exist before the referring item is written, or the write fails on the last field after everything else succeeded.
- The stored access credential expires or is revoked when someone disconnects the site. Detect the authentication failure specifically, mark the connection as needing reconnection, and stop retrying instead of hammering the endpoint.
- If a record is deleted in the app, decide and document whether the item is archived, unpublished, or left alone. Silently leaving orphans on a live site is a defensible choice only if it is a stated one.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Field mappings are stored against stable identifiers and survive renames in the designer.
- [ ] Each app record maps to exactly one CMS item, and repeat syncs update rather than duplicate.
- [ ] Empty app values never overwrite existing content in the destination.
- [ ] Draft, archived, and published states are handled explicitly rather than assumed.
- [ ] Rate limits and item ceilings produce backed-off retries and a clear operator-facing message.
- [ ] A revoked or expired connection surfaces as a reconnect prompt, not as repeated silent failures.
- [ ] Publishing is a distinct, reported step whose success or failure is visible in the app.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.