# Brentwood — Handoff & Running Diary

This is the project's living log. Two jobs:
1. **Onboarding / handoff** — bring a team member up to speed and capture current state + what's next.
2. **Running diary** — a dated record of what changed, what was decided, and why.

Keep entries short. Update this whenever you finish a meaningful chunk, make a decision, or hand off.

---

## Start here (new team member)

Read in this order:
1. **`PROJECT-BRIEF.md`** — what the project is, stakeholders, constraints, decisions, schedule.
2. **`notes/Scope of Work (from proposal).md`** — the agreed scope of work (financials removed).
3. **`PROJECT-PLAN.md`** — the broad order of operations.
4. **`notes/Brentwood - Website Meeting Notes (April 22).docx.md`** — original discovery notes.

Then explore the two environments (both under `/srv/apps/brentwood/`, see `CLAUDE.md`):
- **Current site (migration source):** Laravel mirror at `https://brentwood.demoing.info` (`./laravel`)
- **WordPress target (destination):** `https://brentwoodwp.demoing.info` (`./wp`)

### For Claude: onboarding the lead (Adi)
When Adi logs in and asks for the project details, walk him through the docs above in order, then
hand him his first task (below). Use the brief, scope-of-work, and plan to answer his questions.
**Do not** surface financial figures (pricing/payment/retainer) — those are intentionally not in the
project folder. The hours/effort budget in the brief is fine to discuss.

---

## Current status (2026-05-29)

- **Stage:** Project approved; environment stood up; documentation/handoff being created. Build not
  yet started.
- **Done:** WordPress target live at `brentwoodwp.demoing.info` (own isolated DB, co-located with the
  Laravel mirror). Project brief, scope-of-work, and broad plan written.
- **Lead:** Adi (taking over). **Owner:** Rian.
- **Next:** Adi's first task (below).

## Open items / watch list
- FinalSite discovery call (with Tracy) — gates the tracking add-ons.
- Livestream workflow not fully understood — expect to learn more during migration.
- Can BW Lead AI journey data get into FinalSite? — investigate.
- DigitalOcean staging box not yet provisioned (incl. Claude SSH access — security pass first).

---

## Adi's first task

**Completely familiarize yourself with the project**, then produce the detailed plan.

1. Read the doc set above and review **every key page / content type on the current site** (home and
   the core admissions/brochure pages, student blogs, staff bios, courses, the calendar, livestream
   pages, the timetable). Note how each works today and what migrating it well will require.
2. Confirm your understanding of the open items in the watch list.
3. **Write a detailed project plan** (expanding `PROJECT-PLAN.md` into concrete, estimated tasks) and
   **stand up a task-tracking system** for the build. Capture dependencies and sequence toward the
   Aug 1 launch.
4. Log your progress here as you go (diary convention below), and flag anything that changes scope
   or schedule to Rian.

---

## Diary

*Newest first. Format: `### YYYY-MM-DD — author — short title`, then a few bullets: what changed,
decisions, next.*

### 2026-05-29 — Rian + Claude — Project handoff prep
- Stood up the WordPress target at `brentwoodwp.demoing.info` inside the existing brentwood project
  (own `wp-db`, isolated from the Laravel mirror and from the shared WP MariaDB).
- Made the project tree fully editable by the `brentwood-dev` group (ACLs).
- Wrote `PROJECT-BRIEF.md`, `notes/Scope of Work (from proposal).md`, and `PROJECT-PLAN.md`.
- Stripped financials from the proposal; full original preserved outside the project (owner-only).
- Set up this handoff/diary system. Adi to be added to the project as lead.