# Monday — 3-hour handover agenda *Ordered by priority. Everything above the **cut line** is what a 3-hour session realistically holds; everything below it is genuinely droppable — none of it blocks them from using the site.* The through-line: **they should leave able to add a page, add a news post, and fix a mistake, without calling you.** Everything else is a bonus. --- ## Before they arrive (20 min, you alone) - Confirm the front end loads and the Brentwood 100 grid renders (it changed a lot this week). - Open the **Guides** screen once so it syncs — it pulls from the hub on view, and you want that done before you're demoing it. - Have a **real upcoming page** in mind to build together. Building something they actually need beats any demo. - **Post Types Order** is showing "must be configured" — open its settings page and save once, or the Brentwood 100 drag-ordering won't work when you demo it. - Decide who is driving. **Erin should be on her own laptop, logged in as herself**, not watching you. --- ## 1 · Orientation — what this site is (10 min) Front end first, not the admin. Scroll two finished pages and name the sections out loud: "that's a dark panel with a wide photo, that's three photo cards." You're teaching them to *see a page as sections*, which is the vocabulary everything else depends on. Then one sentence, said plainly: **"You don't build sections. You pick one and replace the words."** --- ## 2 · Social connections (30 min — HARD time-box) Do this early, while everyone is fresh and Erin can still phone whoever owns the Meta assets. But **stop at 30 minutes whatever happens** and book a follow-up. This is the one item on the list that can fail for reasons nobody in the room controls, and it must not eat the training. Current state, verified: **both plugins are installed and active, neither is connected to anything.** - **Instagram Feed** (displays the feed — read only) - **Bit Social** (auto-posts *to* social — needs write access, a higher bar) **Erin has to click through both flows herself, logged into her own Facebook/Instagram.** Your "Partner" access on their Business Portfolio is almost certainly not enough: these are app authorisations, and Meta grants them off the roles a person holds on the **Page and Instagram account themselves**, not off partner access to the portfolio. That's why you can't do it for her. Check before you start — it saves the whole 30 minutes if one is missing: 1. Erin is an **admin of the Facebook Page** (not just an editor). 2. The **Instagram account is Business or Creator**, and **linked to that Page**. 3. She can complete **two-factor** on the spot — this is the single most common stall. Order: **Instagram Feed first** (simpler, read-only, proves the account link works), then Bit Social. If Instagram Feed won't connect, Bit Social won't either — don't spend the time. > **If it stalls:** stop, note exactly which screen it died on, and move to item 3. Chasing a Meta > permission problem live will cost you the session and won't fix it any faster. --- ## 3 · Building a page — the core loop (45 min) This is the heart of the session. If you only get through items 1–3, the day worked. **The three steps**, done by you once slowly, then by them: 1. **Add a section** — `+` → Patterns → a Brentwood category → click one. 2. **Replace the words** — click the heading, type. Click the paragraph, type. 3. **Replace the photo** — click it → **Replace** in the toolbar. Then stop and say so explicitly: *that is a finished section.* People expect a fourth step and go hunting for one. **Then the four toolbar buttons** that cover the variations — show all four on the *same* section so the point lands: | Button | What it does | |---|---| | **Swap sides** (↔) | Flips a two-column section. Photo on the left instead of the right. | | **Background** (palette) | White / light blue / light grey / dark grey / none. | | **Card style** | Rounded corners + soft shadow. | | **Curved edge** (on a column) | The signature curve on the photo edge. | Say plainly: *if you want the same section facing the other way, don't look for another pattern — press Swap sides.* **Then build the real page together.** They drive, you sit on your hands. Target 4–5 sections. Expect 20 minutes the first time and 5 the second. --- ## 4 · The safety net (10 min) Deliberately its own item, deliberately before anything else can go wrong. - **Ctrl/Cmd-Z** undoes. - **Revisions** on the Page tab restores an earlier version — show where it lives, and use it once. - Draft vs Publish, and **Preview in new tab** (the button is called **View**). Say: *"If it looks broken, don't fix it — undo."* An admin trying to repair layout by hand is how pages get wrecked. --- ## 5 · News posts (20 min) The thing they'll do most often after pages. - Add a post, title, body, **Featured image**. - **Categories** — use the *Search Categories* box, don't scroll; check before adding a new one. - **The byline** — the single most confusable feature on the site. The *Author* field in Blog Details is the name shown; the sidebar Author is the account that published it. Worth the two minutes. - Putting a **YouTube video** in a post: paste the link on its own line. --- ## 6 · Brentwood 100 (20 min) Rebuilt this week, so it's new to everyone — and it's the piece most likely to impress them. - Add an item: title, text, images. - **"How this tile can look"** — the preview panel. Tick and untick; explain that the grid picks between the ticked versions on each visit. - **Re-Order** sets the numbers — first in the list is #1. - Point out that the grid shuffles on every visit, so a number is a label, not a position. Say it before they report it as a bug. --- ## 7 · Where to get help (10 min) - The **Guides** screen in the admin sidebar. - Search it in plain language — show one real search, and show the "jump straight to" links. - Note it updates itself; they don't maintain it. --- ## ✂ — CUT LINE — everything below is droppable *If you're at 2h45, stop here. The items below are all things they can pick up from the guides, or that can wait for a follow-up call.* --- ## 8 · Staff profiles (15 min) Adding a person, **First Name / Last Name** (the list sorts on Last Name — matters for two-part surnames), and linking a teacher's account so they can edit their own profile at `/my-profile`. ## 9 · Users and roles (15 min) Who can do what, adding a user, and the fact that they sign in with Google rather than the generated password. **Erin has delegated user management**, so this is hers — but it can be a phone call. ## 10 · Menus (10 min) Adding a page to a menu. Deliberately low: restructuring navigation is not a week-one job, and the guide is appropriately cautious about it. ## 11 · Forms and inquiries (10 min) Where submissions land. Flag honestly that *Admissions Inquiries (migrated)* has **no notification set up** — nobody is emailed — so they know before someone reports a missed enquiry. ## 12 · The timetable, livestreams, landing pages, careers (as time allows) All documented, all seasonal. Name them, say the guides cover them, move on. --- ## Things to say out loud at some point - **"Patterns are starting points, not templates."** Once inserted, a section is yours — change anything, delete anything. Nothing is locked. - **"Your existing pages edit the same as always."** - **"Nothing you do is public until you press Update."** - **"If you can't find a box, look for the grey Meta Boxes bar at the bottom."** Every custom field on this site lives in it, and it can open over the whole editor on a new post. ## Known rough edges — don't demo these - Adding a **Gravity Form** in the editor makes the page-background gradient stop short. Cosmetic, editor-only, front end is fine. - The **blog Categories list** is 150+ deeply nested terms and wants a tidy before it's really usable. - **Post Types Order** needs its settings saved once before drag-ordering works (see prep).