# Brentwood — Planning Session Notes (Adi)

User: adi (Adi Pramono), lead developer — personal session log.
Date: 2026-06-02 / 06-03 · Project: Brentwood website migration (Laravel CMS → WordPress)

My own working record of the session where we built the 10-week plan and supporting docs. This is
Adi's personal note (user `adi`) — not a client deliverable.

---

## What we produced

| File | Purpose |
|---|---|
| `10-WEEK-PLAN.md` | Executive / client-facing plan. No per-person task detail, no AI mention, no emojis/bold. |
| `PLAN-INTERNAL.md` | Team working plan — assignments, critical path, header decision, Pages deep-dive, Week-1 SQL. |
| `TASK-BREAKDOWN.md` | Full backlog, 104 items, epics E0–E14. |
| `TASK-TRACKER.md` | Status board + epic-level burn-down (vs ~450h) + append-only burn log + weekly client roll-up. |
| `task-tracker.csv` | CSV export of the 104 tasks for an external tool (Trello/Sheets/Jira). |
| `manual-thought-on-web-dev.md` / `.txt` | My editor-facing block plan (the ~6–8 consolidated custom blocks). |
| `HANDOFF.md` | Diary entries logged for each step. |

Memory saved (so future Claude sessions remember): keep AI tooling out of client docs; no emoji / no heavy
bold in client docs; team initials; the plan-draft status.

---

## Key decisions

- Launch anchor August 1, 2026. 10 weeks: 9 weeks build → launch (Week 9) → Week 10 stabilization (first
  week of the 30-day bug-fix window).
- Team: Rian (owner), Adi (lead — architecture, coordination, final QA), Zeina (assistant — template/design
  + page building), Indra/Rahman/Yohana (juniors — page building & content migration). Juniors are one
  shared pool, not siloed. Coordination is Adi's, not Zeina's.
- Critical path = blocks gate page building. Week 1: core blocks + page prep. Week 2: finish blocks +
  template, page building starts in parallel.
- Header: build in Kadence (client-editable) with child-theme override only where Kadence can't match.
- Pages = 3 workstreams: block library (T1 static / T2 composite / T3 dynamic-Vue-rebuild), re-runnable
  extractor, page assembly tiered A/B/C. Bespoke per-page overrides are few — most pages bulk-migratable.
- Blocks: the ~25 surveyed layouts collapse to ~6–8 real custom blocks with layout options (Hero Media,
  Page Title, Text+Dual-Image, Video, Interlink, Table-link, Testimonial) + Kadence Row / Adv Query Loop
  for a couple + CPT-driven lists (livestream/news/search).
- Client doc rules: no AI/Claude mention (our private tool), no emojis, no heavy bold.
- Framing: Week 4 = "first complete draft → polishing & mobile refinement" (avoid the word "rough").
- Added a "What we need from Brentwood" column; client checkpoints at Weeks 5, 7, 8. Week 8 is the buffer.
- Editor friction addressed in Week 8 (118 permissions → ~8 roles + content-approval workflow);
  performance + backups + image optimization in Week 6.
- Change-control note: client routes changes through Rian; don't edit staging directly; light freeze near
  launch.

---

## Open items / next steps

- Confirm the launch day — August 1 is a Saturday. Options: weekend cutover (team standby, full support
  Mon Aug 3) or a weekday. Flagged in the plan as "to confirm." My lean: keep Aug 1 cutover, support Monday.
- Run the Week-1 DB tiering counts (E0-1). Needs DB access — either run the extractor inside the Docker
  network (the WP container can reach the Laravel DB as host `mysql`) or Rian temporarily exposes the
  Laravel MySQL on `172.17.0.1:<port>`. This firms up the estimates.
- mysql-data → WordPress: feasible. The `mysql-data/brentwood` dir has all 51 Laravel tables (raw InnoDB —
  must be read through a MySQL engine, not parsed directly). Convert via the extractor (E4). Migrate
  content only — NOT users / password_resets / personal_access_tokens.
- FinalSite discovery call (with Tracy) — gates the campaign tracking. Arrange ahead of kickoff.
- Decide with Rian before the Week-2 block sprint: consolidate Video/Interlink layouts? drop the lightbox
  "+" icon (→ Kadence Row)? dark mode (only on /arts/arts-gallery — recommend skip)?
- Build the hours-vs-budget burn model once counts are in.
- Per-content-type deep-dives still worth doing (Staff/Courses/Blogs/Calendar/Livestream) like the Pages one.

---

## Notes to self
- The exec plan is the client-clean one; the internal plan + tracker + backlog hold the real detail.
- Don't surface exact content volumes (700+ blogs etc.) to the client until the Week-1 count confirms them.
- Estimates are provisional until E0-1 runs; rough epic total ~480h vs the ~450h ceiling — re-baseline after.