# WordPress Post Publishing

## Objective

Publish app content to a WordPress site with media, taxonomy, and post status intact.

A publishing path that creates and updates WordPress posts from app records, including uploaded media and assigned taxonomy.

## 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 operator register the target site once and store the resolved host, then validate every outbound request against that stored host so a user-supplied address can never point the app at an internal network service.
2. Authenticate with a credential scoped to the narrowest role that can publish, hold it encrypted on the server, and never expose it to the browser or include it in a client-rendered configuration blob.
3. Upload media first, confirm each upload, and only then create the post that references it, carrying alt text and attribution across so the published article is not a page of broken image frames.
4. Keep a persistent link between the app record and the created post so subsequent saves update it, and support the site's draft, scheduled, and published states explicitly rather than always publishing immediately.
5. Sanitize the content against the markup the target site actually permits before sending. Do not assume the destination will clean it up — pushing raw user-authored markup into a publishing endpoint is how one app's input becomes another site's stored script.

## 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

- Only hosts an administrator configured may be contacted. Accepting an arbitrary site URL turns this feature into a request-forgery tool pointed at whatever the app's network can reach.
- The credential must carry the least capability that works. A full administrative account stored for convenience means a leak of the app's database is a full takeover of the customer's site.
- Media uploads fail independently of the post. A post created with references to uploads that did not complete must be held back or repaired, not published with missing images.
- Slugs collide. Two records with the same title will fight over one slug, so decide whether the app disambiguates, updates the existing post, or refuses, and make the outcome visible.
- Scheduled posts depend on the destination's own time zone, not the app's. A time sent without an explicit zone will publish hours early or late.
- Content that survives the app's own editor may still be stripped or mangled by the destination's allowed markup. Sanitize to the target's rules and show the operator what was removed.
- Sites go down, plugins break the endpoint, and requests time out mid-write. Retry with backoff on transient failures, key the retry so a post created before the timeout is updated rather than duplicated, and tell the user plainly when the site is unreachable.
- Deleting or unpublishing in the app needs a defined effect on the live post, and the app must not assume it still has permission to make that change.

## 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

- [ ] Outbound requests reach only administrator-configured hosts.
- [ ] Credentials are stored server-side, encrypted, and scoped below full administrative capability.
- [ ] Media is uploaded and confirmed before the referencing post is created, with alt text preserved.
- [ ] Draft, scheduled, and updated posts all work, and scheduling uses an explicit time zone.
- [ ] Slug collisions resolve by a stated rule instead of creating silent duplicates.
- [ ] Content is sanitized to the destination's allowed markup before transmission.
- [ ] An unreachable site produces a clear message and a bounded retry, never a duplicated post.
- [ ] 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.