A group trip website everyone can check without asking you
On a group trip, the organiser becomes the help desk. A single page with the dates, how everyone's getting there, who's sharing which room and what to pack answers most of the questions before they're asked. Keep it to what's safe on a public page; booking references and addresses go in a private message.
Why a page beats a spreadsheet and a chat
Group trips usually run on a shared spreadsheet and a group chat. The spreadsheet is accurate but hard to read on a phone; the chat is easy to read and impossible to search. A page sits between them: one link, readable on a phone in an airport queue, laid out in the order people need it. You still keep the spreadsheet for the money and the chat for the jokes.
What goes on it
- The headline facts: where, the dates, and the one time everyone has to be somewhere.
- Getting there: who's on which flight or train, by first name only, with departure and arrival times, and a meeting point.
- The plan, day by day: a short schedule with times and what to wear or bring for each part.
- Rooms: who's sharing with whom, by first name, and the check-in time.
- Packing: what's needed beyond the obvious (passport validity, adaptors, a costume, walking boots).
- Money: what's already paid, what's owed, and how to pay it.
- Who to call: the organiser and a deputy, in case the organiser's phone dies.
For a stag or hen do, add a dress code for each night and anything the guest of honour must not see. For a family trip, add children's needs and nap-friendly plans.
What to leave off
Published Anticode pages are public, with no password protection, and each site serves a sitemap. A page that reads "the house is empty from 3 to 10 June" next to a surname is useful to the wrong people. Keep these in a private message instead:
- Booking references, PNRs and confirmation numbers (they can be used to change or cancel bookings)
- The exact address and door codes of where you're staying
- Full names, passport details or dates of birth
- Home addresses and the dates homes will be empty
Name the town and the type of place ("a farmhouse outside Lagos, Portugal") and send the address to the group on the day.
Keeping it current
Plans move: a flight time changes, someone drops out, the Saturday dinner is rebooked. If the day-by-day schedule lives in a CMS collection, with fields for day, time, what and where, you edit an entry in the dashboard and the page updates without a rebuild. Smaller edits, like a changed meeting point, can be made in place in the visual editor. Recent saves are kept in version history, so if you get something wrong you can restore the earlier version.
Questions and money
Add the contact form, which asks for a name, an email and a message, for people to send dietary needs, flight details or questions without cluttering the chat. Each one is saved in your dashboard and can be emailed to you. If people owe a share of the villa or a group activity, a payment link from PayPal or another provider you use can sit next to the amount. For splitting costs as the trip goes on, a separate bill splitter app can help.
Building it
Describe the trip: "a trip page for eight friends going to Lisbon, 12 to 15 June, with flights by name, a day-by-day plan, room shares, a packing list and what everyone owes". Playful (Fredoka) suits a stag do; Editorial (Geist) suits a milestone trip. Publish it on a free anticode.dev address and pin the link in the chat.
Limits
- No live flight status or maps. Pages run no scripts and pull in no live data; link to the airline or a map app instead.
- No logins or private pages. Keep sensitive details off.
- No expense tracking on the page itself.
- Patchy signal abroad. Every published site can be installed on a phone and has an offline fallback page, but that isn't the same as the itinerary being readable offline. Screenshot the times and meeting points too.
Questions people ask
Can everyone in the group edit the page?
Only people with access to your project, such as members of a Team workspace. Most groups are happier with one organiser editing.
How do I take it down after the trip?
Unpublish it from the dashboard, or replace the plan with a few photos and keep it as a souvenir.
Can people RSVP for optional activities?
They can say so through the contact form. For separate questions, a custom form tied to a site function can have up to 30 plain-text fields; for set choices to tick, an app build can have its own form fields.