Real client project
Farmhouse Toronto: turning event assets into one focused ticket journey.
TicketPortX supplied the event brief, ticket widget, flyer, photography, video, and brand direction. Allen designed and delivered the original responsive landing page around those materials.
- Client
- TicketPortX / Farmhouse Toronto
- Deliverable
- Event landing page and source package
- Allen's role
- Design, development, revision, QA, handoff
- Status
- Original delivered version, not presented as current live work
01 / The request
Create the page, connect the ticket experience, return the complete files.
The initial request was for custom event landing pages built from information and assets supplied by TicketPortX, then returned as HTML, images, and project files. Farmhouse Toronto was selected as the first engagement.
The specific direction called for a modern, high-design presentation that matched the flyer, used a looping video treatment, placed event details and the ticket experience together, and left room for additional Farmhouse events later.
Client supplied
A complete event content kit.
- Event name, date, time, venue, ticket price, and description
- TicketPortX event link, embedded widget, and purchase requirements
- Farmhouse flyer, logos, photography, and motion clips
- Instagram destination and organizer context
- Style direction based on the event artwork
Allen built
A branded page with one clear purchase destination.
- Custom one-page event architecture and visual direction
- Hero, event details, gallery, motion reel, organizers, and future-events structure
- Embedded TicketPortX widget and on-page ticket navigation
- Browser-friendly versions of supplied motion assets
- Responsive code, quality checks, documentation, and delivery package
02 / Build record
What was completed.
Every major section came from the supplied event brief and real media rather than placeholder content.
- 01
Event narrative
Organized date, time, venue, price, description, artwork, and ticket actions into a clear sequence from first impression to purchase.
- 02
Brand-led visual system
Derived the colour, typography, rounded panels, motion, and party-focused rhythm from the supplied Farmhouse flyer and creative direction.
- 03
Motion and media
Built a repeating hero treatment, a four-video motion section, animated logo moments, and a responsive photo gallery from the client's assets.
- 04
TicketPortX integration
Embedded the client's ticket widget in the purchase section and maintained a reliable ticket path inside the event page.
- 05
Future-ready structure
Included an area that could support up to seven planned Farmhouse events without rebuilding the whole experience.
- 06
Complete handoff
Prepared the final HTML, CSS, JavaScript, images, videos, browser fallbacks, README, and customer work summary as a clean delivery package.
Documented revision
Keep the visitor on the event page.
Review feedback changed the ticket interaction and refined the presentation before final delivery.
- Review request
- Make Buy Tickets move visitors to the embedded ticket area instead of immediately sending them to another page.
- Implemented change
- Updated the ticket buttons to scroll directly to the on-page TicketPortX widget and removed the extra TicketPortX label beside the video.
- Final polish
- Compacted the gallery, improved face and head cropping, added restrained motion, and corrected the fallback ticket text.
03 / QA and delivery
Media-heavy without abandoning browser reliability.
Supplied MOV files were converted to MP4 for broader browser support while the originals remained as fallbacks. Offscreen media was paused or delayed where practical, and unnecessary background-video load was reduced.
The final revision was checked across desktop, tablet, and mobile for broken local assets, horizontal overflow, gallery framing, video source selection, console errors, ticket navigation, and Safari or mobile rendering issues.
The delivered folder included only the customer website files, assets, documentation, and final work summary. Working notes, QA screenshots, duplicate folders, and internal files were kept outside the handoff.
Evidence boundary: This page shows the original delivered version and its documented revision history. It does not present the archived event as a current live site or claim ticket-sales results.
Have the flyer and event details ready?