Horizon Summit 2027: a conference website built by an AI agent
A complete three-day conference site with a filterable agenda, speaker and session pages, calendar downloads and a members-only attendee ...
For each Raytha use case we take a realistic brief, hand it to an AI agent with the raytha CLI, and publish what
comes out: the site, the files behind it, and a kit you can use to rebuild it yourself. This one is a wedding
website for guests: the couple's story, the weekend schedule, how to get there and where to stay, things to do
nearby, answers to the usual questions, the registry, a gallery and an RSVP form that really works.
The agent built it on a fresh Raytha 2.0.1 instance. Nobody opened the admin. Every template, content type, story chapter, event, hotel, page, form handler and menu went in through the CLI, from files in a directory.
What was built
Maren & Ezra are a fictional couple getting married at an orchard in the Hudson Valley. Their site has:
- A home page with their names set large, the date and place, a live countdown to the ceremony, a note from the couple, the weekend at a glance, the first chapters of their story, a few gallery postcards and a call to RSVP.
- A schedule for all three days, from Friday's welcome drinks to Sunday's farewell brunch. Every event shows the time, venue, address, dress code and a map link, has its own page, and can be added to a calendar in one click. There is also a calendar file for the whole weekend.
- A travel page with the train, plane and car options and room blocks at three hotels. Each hotel card shows the group rate, the booking code and whether the wedding shuttle stops there, and counts down to the day the block closes.
- Twelve things to do nearby, filterable by eat, drink, outdoors, art and history, and shop, each with a short note from the couple.
- Their story in six illustrated chapters, an FAQ grouped by topic, a registry page with four registries that open on their own sites, and a gallery of illustrated postcards that open in a lightbox.
- An RSVP form that really works. Guests say whether they can come, how many are in their party, which events they will attend and what they would like for dinner. Replies are checked on the server and saved as private drafts that only the couple can read.
- A guest page behind a sign-in, with the shuttle timetable, day-of phone numbers, the after-party, the shared photo album and a list of babysitters. The after-party also appears on the schedule, but only for signed-in guests.
The design feels like good wedding stationery: warm paper, deep forest green and a terracotta accent, with arch-shaped frames, small botanical sprigs and a round date seal. Headlines are set in Cormorant Garamond, a classic book serif with a beautiful italic ampersand, and the text is Figtree, a friendly sans-serif. The pictures are illustrated landscapes drawn by a script, so every image is license-free and no real people are shown. On a 390px phone the menu folds away, the countdown fits on one row and the RSVP form stacks into a single column.
How the RSVP works
Raytha does not have a form builder, but it does have Raytha Functions: small JavaScript programs that answer HTTP
requests at a path you choose. The RSVP page is an ordinary HTML form that posts to a function at forms/rsvp. The
function:
- Ignores the submission if a hidden "website" field is filled in. People never see that field; spam bots fill it.
- Stops accepting replies after the RSVP deadline.
- Trims every value to a sensible length and checks that there is a name, a valid email address and an answer to "Can you come?". For guests who are coming it also checks the party size and dinner choice, and keeps only the events that are really on the schedule.
- Saves the reply as a draft in an RSVPs content type that has no public pages.
- Sends the guest to a thank-you page that greets them by name, with different wording for yes and no, or back to the form with a short explanation of what to fix.
The couple read replies in the Raytha admin like any other content. A second function, calendar.ics, builds the
calendar files from the schedule, so changing an event's time in the admin updates every guest's download.
The guest page
Raytha has public user accounts and user groups. Guests are added to a "guests" group, and the guest page's template checks the visitor's groups on the server before it renders anything private. Everyone else gets a short sign-in card, and the private details are never in the HTML at all. The schedule works the same way: the after-party is marked "only for signed-in guests", so it is left out of the page and out of the calendar file unless a guest is signed in.
Features, and the Raytha features behind them
| Feature | How it is built |
|---|---|
| Story, schedule, hotels, things to do, FAQ, registry, gallery and RSVPs | Eight content types from one schema document. Events use a dropdown for the day and a checkbox for guests-only events, hotels a date for the block cut-off and a color for each card, places and questions a dropdown for the kind and topic, and story chapters and photos an attachment for the illustration. |
| 55 seed items | Content import from JSON Lines, with the illustrations uploaded during the import. |
| Schedule, things to do, FAQ, registry, gallery and story | Six list views with their own Liquid templates. The things-to-do template checks ?kind= against the known kinds and builds a filter for get_content_items. |
| Countdowns | The templates write the ceremony time and each hotel cut-off into the page, and a few lines of script turn them into a ticking countdown and "Rooms held for 216 more days". |
| RSVP form | A plain HTML form that posts to a Raytha Function, which checks the fields and calls API_V1.CreateContentItem to save a draft. |
| Calendar files | A second Raytha Function that returns an .ics file for the whole weekend or a single event. |
| Guest page and guests-only events | A user group and a server-side check of the signed-in user's groups in Liquid, plus restyled sign-in templates. |
| Private RSVPs | The RSVPs list view is not published, and drafts have no public page. |
| Home, Travel, RSVP, Thank you and Guest page | Site pages built from 12 custom widget templates (hero with countdown, welcome note, weekend at a glance, story teaser, gallery strip, call to action, page header, getting there, hotel blocks, RSVP form, thank-you, guest details). |
| Navigation | Two menus: the main menu and a footer menu. |
The brief
This is the brief, as given to the agent.
Build a wedding website for guests on a fresh Raytha instance with the
raythaCLI. No clicking around the admin.
Look and feel
- Visually impressive, with a design of its own. Display type that is well proportioned, not overly wide or squished.
- Responsive. It has to look good on a phone as well as a desktop.
Content and pages
- The couple's story, the schedule of events, travel and hotel blocks, things to do, an FAQ, registry links to other sites, and a photo gallery.
- A working RSVP that saves replies privately, with spam protection. Optionally, a page only guests can see.
Done means
raytha checkpasses with no broken routes.- Screenshots of the result on desktop and mobile.
- A kit in the examples repository that rebuilds the site on a fresh install.
How long it took
About 40 minutes of agent time, from an empty install to raytha check passing on every route, including the
visual design, the generated illustrations, the two functions, the guest page and writing all of the content.
Rebuild it yourself
The theme, schema, seed content and illustrations, page definitions, functions and menus are in the
raytha-examples repository,
with a build.sh that rebuilds the whole site into any Raytha 2.x instance. Point it at your site with
RAYTHA_URL and RAYTHA_API_KEY and run it.