The inverse of every other page here. Its job is to withhold.
For convenings under the Chatham House Rule where the guest list, the agenda, and the speakers are all confidential — but the page still has to load publicly for registration to work.
Notes
Publicly reachable is a hard requirement of the embed — the page must load without a login for Gatsby to display it. Design accordingly: assume the URL will be forwarded.
Pair with a private Gatsby event so the guest list is protected even though the page isn't.
The prompt
Create a landing page for [FORUM NAME], a closed-door convening hosted by [YOUR ORGANISATION] on [DATE] at [CITY — do not name the venue].
CRITICAL: this page is publicly accessible to anyone with the link, but the event is confidential. It must convey seriousness and exclusivity while revealing almost nothing specific. Withholding is the design brief, not a limitation to work around.
Include:
1. A restrained typographic hero: forum name, "By invitation", the city, and the month and year. No full date, no venue.
2. Two or three sentences on the forum's purpose and the kind of people who attend — described by role and seniority only. "Twenty-five investors and operators." Never names, never firms.
3. A note on the format: roundtable, closed session, duration in broad terms. No agenda, no session titles.
4. A clearly stated Chatham House Rule paragraph, in plain English — what may be shared afterwards and what may not.
5. A confidentiality note: no recording, no press, no social posting.
6. A line saying venue details and the full agenda are sent directly to confirmed attendees.
7. A minimal footer: organisation name and a contact email placeholder.
Do NOT include: speaker names, attendee names, firm names, a venue name or address, a map, a photograph of the venue, session titles, or a sponsor section.
Design direction: severe and quiet. Near-monochrome. One serif or one high-quality sans, used consistently. Substantial whitespace. Small type set generously rather than large type set tightly.
The page should feel like a printed card rather than a website. Someone forwarded this link should immediately understand it isn't for them.
Motion: a single slow fade on load. Nothing after that.
Two requirements that govern how this page will be used:
FIRST — this page will be embedded inside a Gatsby event page, which supplies its own RSVP frame on top of it. So:
- Do NOT include any RSVP button, register button, ticket link, "reserve your spot" call to action, or registration form. Gatsby provides all of that.
- Do NOT include a contact form, a newsletter signup, or an email capture of any kind.
- Do NOT include a sticky header or floating action button that could collide with the RSVP frame overlaid on top.
- Leave roughly 120px of clear vertical space at the very bottom of the page so the Gatsby RSVP frame has somewhere to sit without covering content.
If a section feels like it needs a call to action, end it with a line of text instead — the Gatsby frame is the button.
SECOND — publish it to a public URL that requires no login, no password, and no invitation. I need to open it in a fresh incognito window and see the whole page with no wall of any kind, because it has to load inside an iframe.
Do not enable any preview password, access gate, or authentication. If your platform sets a Content-Security-Policy with `frame-ancestors 'none'`, remove it or change it to `frame-ancestors 'self' https://gatsby.events` — otherwise the page will refuse to load inside Gatsby.
Build requirements:
- Fully responsive, designed mobile-first. Most guests open event pages on a phone.
- No horizontal scrolling at any width from 320px up.
- Real, specific placeholder copy throughout — never lorem ipsum. I need to see how actual text sits in the layout.
- Descriptive alt text on every image.
- Keep it fast. Avoid heavy video backgrounds and multi-megabyte hero images; this loads inside another page.
- Respect prefers-reduced-motion for any animation.
