A simple one page wedding website,
written from one prompt

Search for a simple one page wedding website and you land in template galleries: a skeleton inside a builder, a builder account to use it, and behind most of them a registry you did not ask for. The template was never the hard part; the hard part is that the page ends up living inside someone else's product.

Here the template is a prompt. Paste it into Claude with the Hostus connector on: it proposes a palette and the order of the blocks, waits for your yes, writes one HTML file with the date, the day, the place, travel, dress code, an RSVP and a question box, and publishes it on a link. It is the wedding pair of the link in bio prompt: same method, different page.

What it produces

Here is the result, live: a fictional couple's one page wedding website made from the prompt below. Names and date on top, then six blocks: the story, the day, the place, getting there, questions, and the RSVP, with Ask on. The couple, the venue and the hotel are made up and every date and number is illustrative, but the page is real: open it on your phone, ask it "is there parking?" and send a test RSVP.

Nothing asks a guest to sign in and nothing sells them a gift. It is one HTML file on the free plan, and Google Fonts is the only thing it loads from outside.

What one page needs, in order

A wedding page is read once, on a phone, so the order of the blocks matters more than the design. This is the order the prompt asks for.

• Names, date, place, hour. The first screen answers what a guest wants to know before reading anything else. No countdown, no carousel.
• The story, short. Three or four sentences that set the tone.
• The day. A schedule with times: arrive, ceremony, drinks, dinner, music, the last shuttle.
• The place. The venue, a map link, one line on terrain and weather.
• Getting there and where to stay. Shuttles, parking, a hotel block with the name to give and the hold date. The block you will update most.
• Questions. Dress code, children, gifts, plus ones. Written as questions and answers on purpose: that is the text Ask will cite.
• The RSVP, last, with a close date. Name, coming or not, how many, meal, dietary notes, a song, a message. One form, one button.

Not on the list: a menu with pages, a registry, a guestbook, a countdown, a gallery. The Joy alternatives page compares the platforms that lead with a registry; the wedding RSVP guide covers how the form stores replies without a backend and closes on the date. This page is about the page itself and the prompt that writes it.

The prompt

Paste the whole thing into Claude with the Hostus connector on, fill in the brackets and delete what does not apply. The confirmation step matters most: it comes back with a palette, two typefaces and the blocks in order, and waits for your yes.

Make me a simple one page wedding website for [Ana] and [Tomás], [Saturday 14 March 2027], at [venue, town], ceremony at [15:00].

WHAT I AM GIVING YOU
- Our story, in a few lines: [...]
- The day: [times for arrive, ceremony, drinks, dinner, music, last shuttle]
- The place: [what it is, a map link, the terrain]
- Getting there and staying: [shuttles and times, parking, hotel: name, rooms held, hold date]
- Questions guests will have: [dress code, children, gifts, plus ones]
- RSVP by: [1 February 2027]
- Palette: [from the attached photo] or [two colours in hex]

WHAT TO DO FIRST
1. Propose in one short message: five colours with the job each one does, a serif for the names and a sans for the body, both on Google Fonts, and the blocks in the order you plan to use them. Only build after I confirm.
2. Then build the page.

THE PAGE
- One HTML file, mobile first, one column, about 620px max, large tap targets, iPhone safe area
- No dependencies beyond Google Fonts. No framework, no build step, no second file
- A typographic hero: names, date, place, hour. No heavy images: at most one small photo, under 150 KB, embedded
- Six sections with ids: our-story, the-day, the-place, getting-there, questions, rsvp. Small anchor links under the hero, not a menu
- The schedule as a list with the time on the left
- The questions as question and answer pairs, the answer in the first sentence
- The RSVP is a <form method="post" name="rsvp"> with named fields: name, email, attending (yes or no), guests, meal (fish, meat, vegetarian), shuttle (no, or a time), notes (allergies, children and ages), song, message. No action URL, no backend, no key in the page. One button, and one line under it: a thank-you appears here after sending, and the answer reaches us by email
- Calm copy, no exclamation marks, no emoji. Static under prefers-reduced-motion
- Render it at 390px wide and check line breaks and contrast

Publish it to Hostus and give me the link. Then set the form to email me per response, with the success message "Thank you, we have your answer. See you in March." When I come back on the RSVP date and say so, close the form and leave the page up.

The page is born private: switch it to public in the Hostus dashboard before you send the link, or to email-gated if you want only guests who type their email to get in, still with no account, and you see who opened it. Ask and Reply are already on.

Two lines do most of the work. The confirmation step stops the assistant from repainting a generic template in your colours. And the questions written as pairs are what make Ask useful later: when a guest types "can I bring the kids?", the page has a sentence to cite.

What to change after

Every change is the same move: ask Claude through the connector, or paste the file back and ask, and the new version goes up on the same link. Replies stay in the inbox; previous versions stay in the history.

• The hotel block. "Add Hotel X under Casa do Vale, same format, hold until 1 February" is the whole request.
• The schedule. The shuttle times move. Ask for the day block and the shuttle options in the form to change together.
• A new question. Ask lists what the page could not answer, in the guests' own words. Add the common ones to the questions block.
• A new date. It is in the hero, the RSVP heading and the success message; ask for all three.

The file is yours; if you ever leave Hostus, it goes on any host as it is.

How guests use it

A guest opens the link on a phone like any web page: no app, no download, no account. They scroll from the names to the form in under a minute and press one button. The thank-you appears in place of the form, with a short "Form by Hostus" line under it, and the reply is in your inbox on the document and in your email.

When the page does not say what they want to know, they ask it. Ask is on by default: a guest types "is there parking?" and gets a short answer from the page, with the section cited. It answers what you wrote, not what it guesses; what it cannot answer lands in a list for you. The free plan allows 20 reader questions a day across your account, the paid plan 200.

A guest can also leave a private note on a section with Reply: "we will arrive after the ceremony", anchored to the schedule. Only you see it, you get an email, and you answer from the dashboard or the connector. Reading by section shows which blocks guests open and for how long.

Hostus first, then the builders: which one to pick

Hostus. Best if you want the wedding page as a page of your own, written from a prompt, with an RSVP that reaches your email and guests who can ask the page. The prompt above is the template; the free plan has no clock, no card and 100 form replies a month. No registry and no guest list manager, on purpose.

Zola. Pick it if you want registry, guest list manager and stationery in one place. Its site says the wedding websites are free to create and publish, with online RSVPs and meal preferences, a registry guests browse without leaving the site and a synced guest list; the paid part is a custom domain, from $17.99.

Joy. Pick it if you want the same bundle with online invitations. Its site says the website is "completely free, including RSVP tools, templates, and hosting", with planning tools and registry free as well, and online save the dates and invitations in free designs plus premium paid ones. A custom domain is extra; its FAQ says one typically costs $20 to $40 a year.

The Knot. Pick it if you already plan on The Knot and want the website next to the vendors and the checklist. Its help center says the websites are completely free, with RSVP collection, registry integration and guest messaging; a custom domain is the optional upgrade, $19.99 for a year or $39.98 for two.

Minted. Pick it if the website should match the printed invitations. Its site sells free wedding websites with online RSVP, registry pages and privacy settings on an address ending in .minted.us; a custom URL is an upgrade its help center lists at $15 a year.

A template on Wix or Squarespace. Pick it if you want a visual editor and several pages, and are fine with a builder account and its plan; the site stays inside the builder.

Side by side

Vendor facts were read on each vendor's own site on 18 October 2026 and change without notice; "Check their site" means the vendor did not publish the fact on the pages we read.

Good to know before you switch

The free plan allows 100 form replies a month across your account; replies past that are held, not lost, until you upgrade, and the paid plan has no limit. There is no registry, no guest list manager and no seating chart: the page is the page and the replies. The address is your-names.hostus.page, with no custom domain on any plan, and every page carries a small "Published with Hostus" pill in the corner. The gate, if you want one, is by email rather than a password: a guest types an email, with no account, and you see who opened the page.

Public pages carry a noindex and do not appear in Google, the right default for a wedding. Hostus does not email the guest who replied; the thank-you on screen is their confirmation. If you want guests to see who else has said yes, that is the RSVP page with page storage, a different build.