# Project Brief - 2RE03 Portfolio Site

> Foundation document. Shapes all other memory-bank files and is the source of
> truth for scope. Last updated: 2026-09-22.

## Overview
Build a portfolio website for the design company **2RE03**. The primary focus is
**web design**, but the company can do **any kind of design work**, so the site
must present a broader design capability rather than websites alone.

The site is a client-facing portfolio: it showcases work and communicates what
the company does, with a distinct personality.

## Core Requirements
- Showcase design work across categories: web, print, logos, 3D modeling, and
  written/designed pieces.
- Establish the company as capable well beyond web design.
- Give prospective clients an easy path to understand services and make contact.
- Carry the company's personality/tone throughout the copy (see
  `productContext.md` → Tone & Voice).

## Brand Basics
- **Company name:** 2RE03 (wordmark styled "2RE03", per `refrence/index.html`).
- **Parent-brand context:** the source material mentions "2RE Factory" as an
  umbrella, but **the site must not include it - the brand is purely 2RE03**
  (decided 2026-09-10).

## Scope
### In scope
- Marketing/portfolio site for 2RE03.
- The five work categories above.
- Hero, Case Studies, Work, About, Services, and Contact sections.
- A Collins-inspired **case studies index** (typographic list + hover previews)
  plus per-project **case study detail pages**.

### Out of scope / constraints
- No attribution of work to a named individual (present all work as company work).
- No invented facts about the company or the CEO.
- `refrence/` is temporary source material, not delivered assets, and must not be
  linked to from the site.

## Success Criteria
- Clear, fast, characterful portfolio that reads as confident and crafts-focused.
- Work is browsable by category with images and short, intentional captions.

## Ways of Working (Process Rules)
1. **Plan, then build.** Agree the plan in the memory bank before generating
   production code; record decisions so they aren't relitigated.
2. **`refrence/` is temporary and not part of the delivered project.** Don't build
   links into it. Don't delete it until the site is designed and approved (the
   user confirms when it can go).
3. **Don't invent facts** about the company or CEO; use only `refrence/` or
   explicit user input.
4. **Keep the tone consistent** (see `productContext.md` → Tone & Voice).
5. **Asset provenance is private:** images in `refrence/img/` were designed by the
   CEO; the site must not mention this.
6. **Small, verifiable changes:** verify each build step (validate HTML, check
   assets resolve, check responsive behavior) before reporting done.
7. **Prefer plain, dependency-light, static output** unless a decision says
   otherwise.
8. **Stay inside the project folder.** Do not create, edit, move, or delete files
   outside `/home/torrey/Documents/Sites/2RE03` (the workspace root). Reading files
   elsewhere is fine. If a task seems to need a write outside it, stop and ask the
   user first. This also means do not move repo files to paths outside the repo, and
   do not delete or write to the external asset backup at
   `/home/torrey/2RE03-unused-assets-backup/`, without asking.
9. **Soft wrap, do not hard wrap.** Do not break lines just to stay under a column limit, in code or in the memory bank: let the editor soft wrap long lines and break only where the structure calls for it. This is a going-forward rule; do not reformat existing files to apply it.

## Source Material
All source material lives in the temporary `refrence/` folder. See
`reference-materials.md` for the full inventory.