# Portfolio Grid

## Objective

Show your projects as a filterable grid, each opening into its own detail page.

A filterable grid of project or case-study entries, each with a cover image and its own detail page.

## 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. Give every project a cover image with fixed aspect ratio, generated server-side from whatever the author uploaded. Reuse the app's existing image processing and focal point cropping rather than trimming with CSS.
2. Put the active filters in the URL so the grid can be shared, bookmarked, and restored by the back button. If the app already has a filter component, extend it instead of writing grid-specific filter controls.
3. Give each project a real detail page at its own URL with its own title and description, not a modal overlay that vanishes on refresh.
4. Load images lazily below the fold and reserve their space in advance, so scrolling a long grid does not stutter or shift what the visitor is reading.
5. Do not rely on a draft flag in the template alone. Filter unpublished projects out in the query that builds the grid and enforce the same check on the detail page.

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

- Mixed aspect ratios destroy the rhythm of a grid. Render every cover into one ratio at upload time and keep the original for the detail page.
- A filter combination that matches nothing must say so and offer a way back, ideally by showing which single filter is excluding everything rather than a bare empty grid.
- Returning from a detail page must restore the filters and the scroll position the visitor left. Losing their place after every project is the fastest way to lose them.
- A grid with dozens of projects must not request dozens of full-size images at once. Serve sized variants and load only what is near the viewport.
- Private or unfinished projects must be invisible to logged-out visitors on the grid, on the detail page, in any search index, and in the sitemap.
- Every cover image needs alt text describing the project, and the detail page needs a proper heading, because these pages get shared far more than the grid does.
- A project with no cover image needs a designed fallback tile, not an empty box or a broken image icon.
- Reordering or deleting a project must not shuffle the remaining tiles under the cursor of someone mid-scroll.

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

- [ ] All cover images render at a single aspect ratio with reserved dimensions.
- [ ] Active filters appear in the URL and survive sharing, reload, and the back button.
- [ ] Returning from a detail page restores both filters and scroll position.
- [ ] A filter combination with no matches shows an explanatory empty state.
- [ ] Unpublished projects are absent from the grid, the detail route, search, and the sitemap.
- [ ] Off-screen images load lazily and the grid does not shift as they arrive.
- [ ] Every cover image has descriptive alt text.
- [ ] 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.