Every save writes to the site's key-value store immediately. The public site fetches those values with a 30-second edge cache, so changes appear within ~30 seconds of saving (sooner if you hard-reload with Cmd+Shift+R).

Photo uploads go to object storage and are served instantly — no cache wait.

You don't touch git, deploy pipelines, or code. Everything happens through this admin UI.

Change the cohort's colors, name, and tagline. Pick a preset palette (recommended — they're guaranteed to look OK together) or open Custom colors for arbitrary hex picks.

Live preview updates as you change values. Nothing is public until you hit Save branding.

If a color choice looks off on the live site, come back and try another preset — no way to break the site.

Steps to get the embed URL from Google Calendar:

1. Open calendar.google.com and sign in with the Google account that owns the cohort's calendar.
2. In the left sidebar under My calendars, hover the calendar you want to embed — click the ⋮ (three dots) → Settings and sharing.
3. Scroll to Access permissions for events → check "Make available to public". This is required for the embed to work.
4. Scroll further to Integrate calendar. Copy the full URL under "Public URL to this calendar" — it starts with https://calendar.google.com/calendar/embed?src=....
5. Paste it into the Embed URL field on the Calendar tab here → Save.

Public URL vs Embed code: both work, but the plain public URL is cleaner. Ignore the <iframe> tag Google offers — we already provide the iframe wrapper.

The calendar can be as simple or collaborative as you want. Three patterns, ordered by how much collaboration you want:

Pattern 1 — Solo admin owns everything. One person creates the Google Calendar, they add events. Members subscribe to it in their own Apple/Google/Outlook calendar. Simplest, but every event goes through one bottleneck.

Pattern 2 — Shared calendar, many editors, one owner. This is usually the sweet spot for a cohort. In Google Calendar's Settings and sharing → Share with specific people or groups, add other cohort members with permission "Make changes to events". Now they can add, edit, or delete events without needing to log into a shared Google account. The calendar is still owned by the original creator (so it can never be accidentally deleted by anyone else), but anyone with edit permission can populate it.

Pattern 3 — Group calendar under a shared inbox. Create a Google Group like emba25-planners@yourdomain, share the calendar with that group as editors. Members of the group can all edit; adding/removing planners = adding/removing group members. Overkill for <10 planners; useful past that.

Common tip: use event Guests to send auto-invites — anyone added as a guest gets an email invite and can RSVP. That's your "event RSVP" flow for free, no extra tool needed.

Add or remove people from the cohort roster. Each row is one person.

Required: Name. Everything else is optional.

Email and phone visibility toggles. Off by default — the member's contact info is stored but only visible to admins. Toggle "show publicly" on if the member has agreed to their contact appearing on the public page.

Notes/bio field: always public if the member is visible. A short blurb about the person, their industry, or a note.

Members render as a grid on the public site. Clicking a card opens a modal with their photo, bio, and any visible contact links.

Admin cards are separate from regular members. They render at the top of the public members section with a "Cohort Admin" medal, always-visible email, and a prominent "Write to [Name]" button.

Purpose: tell cohort members who to contact for changes, event ideas, or corrections — so they're not always coming to the site admin.

Adding a person to admin cards does NOT grant them edit access. Access to this admin panel is controlled separately via Cloudflare Access allowlist (see the Access management section below). Two independent lists.

Multiple admins render side-by-side on desktop, wrapping to multiple rows past ~3 cards. Stack single-column on mobile.

Albums are the organizational layer. Create an album (e.g. "Orientation Trip"), then upload photos into it. Each album can display as a grid (default) or carousel.

Uploading: drag-drop or click the upload area. Photos default to "Unfiled" — pick an album in the Upload to dropdown to assign at upload time, or use the dropdown on each tile to reassign later.

Reordering: drag tiles within the grid to reorder. Order persists automatically.

Reviewing: click any tile to open a preview modal with filename, size, and a delete button. Good for reviewing before removing.

The public site's photos section shows album tiles — clicking one navigates to that album's dedicated page.

The list of people who can log in to THIS admin panel is managed by the site admin. To add or remove an editor:

Email adam.valine@gmail.com with:

1. The editor's email address
2. Which cohort branch they should manage (e.g. EMBA 25)
3. Whether you're adding or removing them

Adam will usually see the email within 24 hours. Once he adds them, the new editor can sign in immediately at the branch's /admin/ URL — they enter their email, get a 6-digit PIN emailed to them, paste it, done. No invitation link needed.

Notes are fed by a shared Google Sheet. Anyone with edit access to the sheet can add or update notes — no admin panel access needed. This lets the whole cohort contribute updates instead of everything routing through a few admins.

Full step-by-step setup lives on the Notes tab. TL;DR: create a Google Sheet with columns Date | Title | Body, publish it as CSV via File → Share → Publish to web, paste the URL into the Notes tab, done.

The public site fetches the sheet every ~5 minutes. New rows appear within that window.

Two most common issues:

1. Changes not appearing. Hard-reload the page (Cmd+Shift+R) to bust the browser cache. If it still doesn't show, wait 60 seconds and try again — the CDN edge cache expires within a minute.

2. Something is broken. Email adam.valine@gmail.com with:

1. What you were doing when it broke
2. Which tab / feature
3. A screenshot if visual, or the browser console output if it's a save failure (Cmd+Opt+I → Console tab → screenshot)