# User Personas And Use-Case Topics

## Purpose

Define who uses this CMS and which feature topics matter for each role.  
This keeps roadmap decisions grounded in real workflows instead of isolated features.

## Primary Personas

### 1. Owner Artist (Primary Operator)

Main goals:

- publish and maintain portfolio website content
- manage artworks, grouped collections, and featured content
- open/close commissions and track incoming requests

Core topics:

- pages + navigation builder
- media library + artwork metadata + renditions
- announcement/banner management
- commissions + customer records
- news/blog updates

### 2. Studio Manager / Assistant

Main goals:

- handle operational content updates and commission administration
- manage customer communication and request statuses

Core topics:

- commission kanban and request triage
- customer profile maintenance
- media organization and moderation
- limited page edits under role constraints

### 3. Content Editor / Social Manager

Main goals:

- publish updates, news posts, and campaign visuals
- keep public-facing content fresh without deep admin privileges

Core topics:

- news/blog authoring
- announcements/promotions
- selected media uploads and metadata edits
- landing page block updates (where permitted)

### 4. Technical Support (Protected Role)

Main goals:

- break-glass access for incident support
- diagnostics and recovery support without owning business content

Core topics:

- support access route/key flow
- protected account safeguards
- operational diagnostics and rollback awareness

### 5. Returning Customer (Commission Client)

Main goals:

- submit repeat commission requests with reduced data re-entry
- track active request state

Core topics:

- customer-linked commission intake
- commission status visibility
- communication and requirement updates

### 6. Public Visitor / Collector / Fan

Main goals:

- discover artwork, updates, and commission availability
- navigate pages and portfolio smoothly

Core topics:

- portfolio browsing (gallery/album/tag/category)
- announcement visibility
- news/blog consumption
- commission request entry points

## Role-to-Feature Responsibility Map

- Owner Artist:
  all core CMS domains
- Studio Manager:
  commissions/customers/media operations
- Content Editor:
  editorial/news/announcements + constrained page/media tasks
- Technical Support:
  operational support only, no business ownership transfer
- Public personas:
  consumption and request flows on public app

## Planning Guidance

When adding a roadmap item, always specify:

1. target persona(s)
2. primary user outcome
3. permissions required
4. public impact (if any)

If an item cannot be mapped to at least one clear persona outcome, it should not be prioritized.