# Press Kit

## Objective

Give journalists your logos, colours, screenshots, and boilerplate on one public page.

A public page of downloadable brand assets, colour values, screenshots, and approved boilerplate copy.

## 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. Serve every asset through the app's existing file download path so that access, headers, and content types are handled the same way as everywhere else, rather than linking directly at raw storage.
2. Store the correct format and media type per asset and derive the filename and extension from the stored record, never from the label an author typed.
3. Present each logo variant on the background it is designed for, and reuse the app's theme-aware asset switching so the page shows the right variant in light and dark rather than a washed-out logo on the wrong panel.
4. Publish the usage rules as text on the page and include them as a file inside every archive, so the rules travel with the assets rather than staying behind on a page nobody bookmarked.
5. Do not build the archive on demand in the web request. Generate it in the background when assets change and serve the stored file, because zipping a large asset set inline will time out.

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

- A bulk download of a large asset archive built during the request will time out or die behind a proxy. Prepare the archive ahead of time and serve it as a static file with a resumable download.
- Light and dark logo variants look broken on the wrong background. Render each on its intended background, label which is which, and never let the page theme swap one for the other silently.
- Superseded assets stay linked from press coverage published years ago. Keep the old URL alive but serve a page explaining the asset is retired and pointing at the current one, rather than deleting the file.
- Vector and raster files served with the wrong extension or content type download as something the recipient cannot open. Match the extension, the stored media type, and the response headers.
- Usage rules that only appear on the page get separated from the files immediately. Include them in the archive and reference them next to every individual download.
- Colour values need to be copyable as text in more than one notation, because a journalist and a designer want different formats.
- Screenshots go stale faster than logos. Show when each asset was last updated so nobody ships a picture of a two-year-old interface.
- The page is public and links to real files, so it will be scraped. Rate limit the archive download and keep individual asset requests cheap.

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

- [ ] Every asset downloads with a filename, extension, and content type derived from its stored record.
- [ ] The full archive is pre-generated and served as a stored file rather than built during the request.
- [ ] Light and dark logo variants each render on an appropriate background and are labelled.
- [ ] Usage rules appear on the page and are included inside every archive.
- [ ] Retired assets keep their URLs and resolve to a page pointing at the current version.
- [ ] Colour values can be copied in more than one notation.
- [ ] Each asset shows when it was last updated.
- [ ] 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.