An event registration page you can publish in minutes
A monthly chapter meeting, a workshop, a community open day, an internal lunch-and-learn. The event is small, the deadline is next Tuesday, and the tooling available to you is wildly out of proportion: a form builder that wants an account and puts its own branding on your sign-up page, or a full events platform that wants a percentage. What you actually need is one page that says when and where, and a box where people put their name.
Write the page the way you would say it out loud
What it is, when, where, who it is for, and the one action you want — sign up. The event prompt below produces that page with the RSVP form already on it, so you are not stitching a landing page to a form tool.
Publish it and switch response collection on
Publish the file, then turn on “collect responses” for the page. Replies land in your responses dashboard, where you can read them as a table, see the summary, and export a CSV for the door list.
Share the link, or the QR code
One URL for the email and the group chat. On a paid plan the page also gives you a QR code, which is what you print on the poster or put on the last slide of a talk.
One page per event, published in minutes
The page is small and always the same shape: date and time, where it is, what happens, who is speaking, and the form. Describe that to an AI assistant and you get a complete self-contained HTML page back in one pass — our templates page has a starter prompt for exactly this. Paste it into host-html, publish, and the registration link exists before the meeting invite has finished being written.
For anything recurring, publish a fresh page per session rather than editing one page forever. Each event then has its own link, its own sign-up list and its own view count, and the previous session's page stays as a record of who came and what was on. A custom slug on a paid plan lets the URL name the session, which is much easier to read out loud at the end of the last meeting.
Collecting the replies on the page itself
Response collection is a paid feature, and it means the form on your page posts back to host-html rather than to a third-party form service. Replies land in a responses dashboard attached to the page, where you can read them, watch them come in and export them. No separate account, no second product with its own logo on your registration page.
That matters more than it sounds for a community or client-facing event, because the sign-up step is where most drop-off happens. A single page that explains the event and takes the reply in the same scroll converts better than a page that bounces the reader to somebody else's form.
If you are on the free plan and just need a date confirmed, a page with your email address and a mailto link still does the job — the form is the upgrade, not the requirement.
Getting people to the page, and what happens after
Every page can generate a QR code, which is the right medium for an event: on the poster in the corridor, on the last slide of the previous session, on a card on the table. The QR and the link point at the same page, so you can measure both together. Views on every plan tell you how many people looked; the responses tell you how many signed up; the gap between those two numbers is the most useful thing you will learn about your event copy.
Afterwards, the page can become the record — the slides, the recording, the notes — at the same URL the attendees already have, using in-place editing on a paid plan. Collections then gather a whole season of events behind a single link, which is how a recurring meeting series ends up with an archive it never had to build.
Publishing is free and a free page expires automatically after 5 days, which genuinely suits a one-off event that is over on Saturday. A series is the opposite case: you want last month's registration page to still resolve, so Pro at $12 a month, where pages live forever, is the plan that fits a cadence.
The form-tool sandwich against one page
| A landing page plus a separate form | One page that does both | |
|---|---|---|
| Setting it up | Two tools, two logins, and a link between them you have to test | One file, published once |
| What the invitee does | Reads a page, clicks through to a form, loses half of them there | Reads and replies without leaving the page |
| Branding | Someone else's form styling in the middle of your event | Your layout throughout, and no badge on a paid plan |
| The replies | Live in the form tool's account, exported when you remember | In your responses dashboard, with a summary and a CSV export |
| A recurring series | Duplicate the form, rename it, fix the link | One page per session, all of them behind one collection link |
What this needs from host-html
- Collecting responses — How the RSVP actually lands: switch it on for the page, replies arrive in a dashboard with a table, a summary and CSV export.
- QR codes and custom slugs — Both are paid features. The QR goes on the poster; the slug is what you read out from a stage.
- The event prompt — Produces the page with the sign-up form already wired to your responses dashboard.
- A series behind one link — Monthly meetup, weekly class, a conference track — one page each, one collection link to share.
Frequently asked questions
How do I create an event registration page?
Generate or write a single self-contained HTML page with the event details and a form, publish it on host-html, and share the link. The whole thing takes minutes and needs no website, no builder subscription and no developer.
Can the page collect registrations, or do I need a separate form tool?
It can collect them directly. Response collection is a paid feature: the form posts back to host-html and the replies appear in a responses dashboard attached to that page, where you can read and export them.
Can I share the registration page as a QR code?
Yes. Every page can produce a QR code pointing at the same URL, which works well on a poster, a slide at the end of the previous session, or a card on the table at the venue.
What happens to the page after the event is over?
Whatever you want. On a paid plan you can edit it in place at the same URL so it becomes the recap — slides, recording, notes — for the people who already have the link. A free page simply expires at the end of its window.
Can I run one page per meeting in a recurring series?
Yes, and it is the pattern we would recommend. Each session gets its own page, link and sign-up list, and a collection groups the whole series behind one link so the archive builds itself.
How many replies can one page collect?
Free accounts do not include response collection at all. On a paid plan the responses dashboard is included with the page, so a normal community event or workshop sign-up list is comfortably within scope.