# EP09 Website Draft

## Goal

Show how portable templates keep a team's operating model from being rebuilt manually each time.

## Hero

**A plugin should carry the team model, not just the files.**

## Page Structure

1. portable bundle overview
2. what should travel together
3. plugin vs loose files
4. template drift examples
5. reusable bundle checklist
6. official links

## Interactive Blocks

### 1. Bundle Map

Show what a portable team template can carry:

- skills
- agents
- hooks
- support notes

### 2. Bundle vs Loose Files

Compare:

- reusable bundle
- ad hoc copied files
- outdated template

Each row should answer:

- what it gives you
- what it risks
- how to keep it aligned

### 3. Template Drift Experiment

Let the reader see how a good template changes when the team changes without being reworked.

## Minimum Viable UX

- editorial, system-oriented layout
- clear bundle boundaries
- no generic marketplace styling
- readable on mobile

## Teaching Rules

- Every portable template must still point to a file home.
- Every example must explain why the bundle exists.
- Every comparison must separate portability from correctness.

## Official Links

- plugins
- skills and plugins
- memory

## Exit Outcome

The reader should know what belongs in a portable bundle and what should remain repo-specific.