Summary: A fast, hand-coded landing page for a multi-day event, with a hero video, a filterable gallery, a consent-gated social feed, a validated inquiry form with a live price estimate, and a content editor mock-up, all on made-up placeholder content.
A build I made for a posted project brief. I built this as a working demo with placeholder content. It is not a delivered engagement, and nothing here is a result from live use.
The problem, as a generic brief
Someone wants a landing page for a small, multi-day event: a header and menu, a hero with video, the program and venue, photo and video galleries, testimonials, prices and rooms, a social media feed, and an inquiry form with confirmation and spam protection. It has to work well on phones, respect cookie consent, and let a non-developer change text, photos, dates and prices afterward.
What I built
A four page demo site with a made-up event brand and placeholder content:
- Main page: announcement bar with a short three question "which one suits you" finder, sticky header with a mobile menu, video hero with a pause button, intro, photo pairs, what is included, venue, a gallery strip with a lightbox, a day by day program, a testimonial carousel, team, prices, a closing call to action, and a footer with a legal pop-up and cookie settings.
- Media page: background video that pauses off screen and stays still for visitors who ask for reduced motion, click to play inline video, a filterable gallery with keyboard, swipe and focus handling, a review slider, and a social feed that only loads after the visitor agrees.
- Booking page: upcoming dates and availability, room cards, an inquiry form with inline validation, an error summary, a shared room versus single room check, a hidden spam trap field, a timing check, a live total with add-ons, and a confirmation state. An editor drawer changes the name, dates, prices and places left and updates the page live.
- How it is built page: the stack, what each part costs to run, and the trade-offs, including that there is no drag and drop builder.
- A private preview gate: a small serverless function that only lets people in with a link key or a PIN, plus first-party visit logging that records usage only after a visitor accepts analytics.
All photos and videos are drawn by a script from code, so the demo ships no stock photos and nothing copied from anywhere.
How it works
- Hand-written HTML, CSS and JavaScript, no page builder, plugins or themes. Fonts are self-hosted.
- Images are served as WebP in two sizes with lazy loading, and the hero video is kept small.
- The inquiry form validates in the browser, shows an error summary a screen reader can follow, blocks bots with a hidden field and a timing check, and updates the total as options change. In a live build, a server function would email the inquiry and a bot check service would sit in front of it.
- Consent comes first. The social feed and usage analytics load only after the visitor accepts. If they decline, that code is never fetched.
- Editing without a developer. In the demo, the editor drawer shows the idea. In a live build, content would live in simple files edited through a browser based editor, saved to a repository and published automatically.
- The gate and the visit log run in Cloudflare Pages Functions with a small D1 database. Visitors are counted with a daily hash, not an IP address, and old rows are deleted automatically.
- Checks: I tested the pages at several phone, tablet and desktop widths, clicked through every interaction, and ran an accessibility and best practices audit.
Stack
HTML, CSS and vanilla JavaScript, Cloudflare Pages and Pages Functions, Cloudflare D1, Python (Pillow, numpy) for the placeholder images and videos, Playwright for browser tests, Lighthouse for audits. Planned for a live build: a browser based content editor, GitHub for version history, and a bot check service for the form.
What I'd do next
- Replace placeholder content with real photos, copy and prices.
- Connect the form to email delivery and add the bot check.
- Connect the real social feed through an approved feed service.
- Launch on a custom domain with the editor set up and a short written guide.
- Run another audit and device pass on the real content.