Twenty-five years ago we said yes to each other in a small town hall, with eleven guests and a borrowed camera. This time we would like rather more of you there.
Come and eat well, dance badly, and stay late.
", "notes": "2–3 sentences from the hosts, in one or two. Centred italic, so keep it under ~330 characters." }, { "name": "schedule-heading", "type": "text", "required": true, "example": "The evening", "notes": "Heading above the schedule. 'The evening', 'The day', 'Programme', 'Agenda' — 1–3 words." }, { "name": "travel-content", "type": "html", "required": false, "example": "
By car — parking is free on the estate; follow the signs at the gate.
By train — Santpoort Noord station is eight minutes away by taxi.
", "notes": "Inside the travel optional. 2–4 short, each opening with a bold mode ('By car', 'By train', 'Taxis home')." }, { "name": "stay-content", "type": "html", "required": false, "example": "
On the estate — twenty rooms are held for us until 5 September; quote De Vries 25 when you book.
In Haarlem — Hotel Lion d'Or, from € 140 per night.
", "notes": "Inside the stay optional. 2–4 shortof hotel suggestions with prices as '€ 140'." }, { "name": "rsvp-heading", "type": "text", "required": true, "example": "Will you join us?", "notes": "Headline of the dark RSVP band. A short question or imperative, under ~30 characters." }, { "name": "rsvp-text", "type": "html", "required": true, "example": "
One reply per household is plenty. Tell us who is coming, whether you would like a room on the estate, and anything the kitchen should know about.
", "notes": "Onesaying exactly what to include in the reply. Under ~200 characters." }, { "name": "rsvp-url", "type": "url", "required": true, "example": "mailto:margriet@devries.nl?subject=RSVP%2026%20September%202026", "notes": "Attribute slot on the button's href. Must include the scheme: a 'mailto:' address (optionally with ?subject=) or an 'https://' form URL. There is no JavaScript, so this is the only way a reply can be sent." }, { "name": "rsvp-button", "type": "text", "required": true, "example": "Reply by email", "notes": "Button label, rendered uppercase. 2–4 words that match what rsvp-url actually does: 'Reply by email', 'Open the form', 'Register now'." }, { "name": "rsvp-deadline", "type": "text", "required": true, "example": "Kindly reply before 5 September 2026", "notes": "Small gold line under the button. One short sentence, ideally under 40 characters so it stays on one line on a phone; write the date out in full." }, { "name": "faq-content", "type": "html", "required": false, "example": "
Champagne & canapés · Weather permitting
", "notes": "At most two short lines (who / where / note), each its own, parts joined with ' · '. Leave empty when there is nothing to add — never a paragraph." } ] } ], "optionals": [ { "name": "travel", "description": "'Getting there' column: driving and parking, public transport, taxis home. Drop it when the venue needs no explaining." }, { "name": "stay", "description": "'Where to stay' column: two to four hotel suggestions with prices. Drop it for daytime or local events." }, { "name": "faq", "description": "'Good to know' section: a question-and-answer list (children, gifts, dietary requirements, accessibility). Drop it when there is nothing left to answer." } ], "changelog": [ { "version": "0.1.0", "date": "2026-08-19", "notes": "Initial release: responsive one-page event site with tinted serif hero, four-cell key-facts strip, schedule repeat, travel/stay/FAQ optionals and a dark RSVP band." } ], "agentInstructions": "Keep event-title to roughly 22 characters (1–3 words): it scales to 84px, so names and occasion belong in event-tagline. hero-dateline is the short poster line (date plus town); the key-facts strip carries the precise data, so write event-date out in full with its weekday ('Saturday 26 September 2026') and keep the two consistent. rsvp-url must be a complete link including the scheme: a 'mailto:' address (optionally with ?subject=) or an 'https://' form URL. There is no JavaScript, so mail or a form is all the button can do — never leave it as '#', and make rsvp-button say which it is. Schedule entries run in strict chronological order with 24-hour zero-padded times ('09:30', '17:00', never am/pm); delete every data-example row and add one 'entry' per item. entry-title stays under 60 characters; entry-detail is at most two short lines joined with ' · ', or empty. Drop the travel, stay and faq optionals when there is nothing real to say. Adapt the register — warm for weddings and anniversaries, crisp for conferences and open days, where schedule-heading becomes 'Programme' or 'Agenda' — while keeping every slot in its declared type. For unknown details, leave visible placeholders like [VENUE ADDRESS] or [RSVP EMAIL] and tell the user to fill them in with the built-in Edit button.", "license": "MIT", "authors": [ { "github": "bvrln" } ] }