# Artist CMS Inspiration Notes

## Scope

Inspiration-only notes for implementation direction.  
These are not direct copy targets and do not override current CMS roadmap decisions.

## Useful Patterns Observed in `gaertan`

### Media and Delivery

- S3-backed storage with signed URL/object access patterns.
- Route-level image streaming/proxy from storage keys.
- Multiple artwork variants/renditions for different view contexts.
- Dedicated actions for generated gallery variants and missing-variant backfill.

### Portfolio Domain

- Artwork linked to galleries/albums/tags/categories.
- Filterable portfolio pages (album/year/tag/search).
- Gallery components designed for responsive/justified layouts.

### Commissions Domain

- Rich commission model:
  - types
  - options
  - extras
  - custom cards
  - custom inputs
- Public request form + admin request management.
- Commission status/kanban-like mapping for intake/in-progress/completed.

### Color and Processing

- Artwork color extraction workflows (palette/tones) from stored image files.
- Potential pipeline point for future theming and discovery filters.

## How We Should Reuse These Ideas Here

- Keep the domain approach, but normalize to current CMS architecture (`@cms/*` packages, Next app router, shared CRUD services).
- Start with deterministic MVP1 primitives:
  - media CRUD + rendition slots
  - portfolio grouping entities
  - commission/customer linking
- Defer heavy media automation (advanced transforms/watermark/palette orchestration) to MVP2 after baseline reliability is proven.

## Guardrails

- No direct schema/code lift from `gaertan`; re-model explicitly for this repository.
- Keep upload and processing abstraction pluggable (S3 now, alternative provider later).
- Favor explicit auditability for media/commission mutations.