# Editorial Brands

Fieldhouse OS is the host application. Import, Screenshots, AI, and Settings are
operational tools that run as Fieldhouse applications.

Published content is rendered inside an editorial brand:

- Home, Scores, and Game Center use Saturday Circuit.
- News, generated articles, game recaps, headlines, social posts, and player
  grade explanations are Saturday Circuit content.
- Future domains, such as coaching decisions, can use a separate brand without
  changing the host tools or Saturday Circuit styles.

## Implementation

`src/renderer/src/editorialBrands.ts` is the brand registry. It owns the brand
name, tagline, and fallback colors, and exposes scoped CSS properties.

`src/renderer/src/SaturdayCircuitSite.tsx` provides the publication chrome:
ticker, masthead, editorial navigation, team edition marker, content body, and
footer.

`src/renderer/src/saturday-circuit.css` is scoped beneath
`[data-brand="saturday-circuit"]`. Team primary and secondary colors skin the
publication through `--team-primary` and `--team-secondary`; the brand retains
its own typography, spacing, rules, and article treatment.

The Fieldhouse desktop and Gridiron Navigator browser chrome remain outside the
brand root. This keeps operating-system and ingestion controls visually stable
as additional publication brands are added.

## Adding A Brand

1. Add the brand identifier and metadata to `editorialBrands.ts`.
2. Create a brand shell component for its masthead, navigation, and footer.
3. Add a stylesheet scoped to that brand's `data-brand` value.
4. Map only the relevant content views into the new shell in `App.tsx`.
5. Register the publication's browser or app entry in `FieldhouseOS.tsx`.
6. Keep imports, OCR review, provider configuration, and settings in Fieldhouse
   applications unless the workflow itself belongs to the publication.