
The short answer: an event, wedding or campaign site has a short life and, near the date, a peak of visits. It is light, and an entry shared plan is enough. The decisions that matter are where to put it (a subdomain of a domain you already have can save a registration) and what to do with it when the event is over.
What weighs, and what does not
| Part of the site | What to do |
| Address | A domain of its own looks more serious and is easy to say. For a short action, a subdomain of the domain you already have will do: Subdomain or folder. |
| RSVPs | A simple form. Test that the messages arrive and that the person gets a confirmation: A contact form that actually reaches your inbox. |
| Guest list | Do not publish it. If you need a guests-only area, protect it with a password: Password protecting a folder. |
| Photos | Shrink them and use WebP: Image optimisation. If they show people, ask permission from whoever appears. |
| The day | Visits bunch up near the date: Preparing for a traffic spike. |
How to choose, step by step
|
|
|
|
| Do not let the domain lapse without deciding. An address that was shared with many people and then vanishes shows an error to whoever opens it. See Domain renewal. |
| If the site is only for the days of the event, a “coming soon” page before and a thank-you page after cover much of what you need: A coming soon or maintenance page. |
|
Making a site for an event or a campaign? Tell us the date and how many people you expect. Open a support ticket |
|
SEE ALSO Subdomain or folder: where to put a blog, a shop or a test site Password protecting a folder with Directory Privacy Preparing for a traffic spike: a campaign, a launch or a live event |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from 5.940,00 Kz/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











