## 09 — Editing the timetable

- **id:** tt-overview
  **path:** /wp-admin/admin.php?page=timetable-management
  **region:** the whole Timetable settings page — the page heading "Edit Timetable Content", the How this works box, and the Content Panels / Academic Block Rotation tabs
  **caption:** The Timetable page. Content Panels and Academic Block Rotation are separate tabs.

- **id:** tt-panel-row
  **path:** /wp-admin/admin.php?page=timetable-management
  **region:** the Timetable Panels list — the first category row opens expanded, showing Heading, Body Text, Panel Image, Block Background Images and the "Learn more" link; the other categories sit collapsed below
  **caption:** An expanded category panel, showing every editable field.
  **capture:** `--selector ".acf-field[data-name='tt_panels']" --trim` — no interaction needed, the
  first repeater row is expanded by default.

- **id:** tt-bg-gallery
  **path:** /wp-admin/admin.php?page=timetable-management
  **region:** the Block Background Images field on the first (expanded) category row — its photo strip and the Add to gallery button
  **caption:** Block Background Images — the faint photos cycled behind a category's blocks in the grid.
  **capture:** `--selector ".acf-field[data-name='tt_gallery']" --trim`

- **id:** tt-rotation-tab
  **path:** /wp-admin/admin.php?page=timetable-management
  **region:** the Academic Block Rotation tab — Rotation Heading, Day Columns, Period Rows and Block Colours
  **caption:** The Academic Block Rotation tab, where the table's days, periods and colours are set.

- **id:** tt-block-sidebar
  **path:** /wp-admin/post-new.php?post_type=page
  **region:** the Brentwood Timetable block's settings panel in the right-hand sidebar (Initial view, Show Academic Block Rotation)
  **caption:** The Brentwood Timetable block's own settings.
  **capture:** must be captured by INSERTING the block on a new page (insertion auto-selects it), with
  `--reset-ui --region block-inspector`. Opening the existing Unique Timetable page (post 1047) and
  clicking the block does NOT select it — it's server-rendered, so the synthetic click lands on inert
  markup and the inspector stays on "No block selected" while still reporting `selectorFound: true`.