Now the festival becomes a real digital product. The website has to combine excitement, information, navigation, accessibility and action. You will plan, wireframe, build and test a multi-page festival website using the platform available to you. By the end of this challenge you will: Design a site map around visitor tasks Create useful wireframes […]
Scan to open this challenge on any device
A festival website has several jobs: excite, inform, reassure and move people toward tickets or another action.
Wireframes help test whether the content makes sense without the distraction of finished branding.
Look past visual style to navigation, content clarity, mobile behaviour and accessibility.
Review one festival site on desktop and mobile if possible. Time how quickly you can find line-up, travel and accessibility information.
Compare two festival sites using five criteria: navigation, hierarchy, mobile readability, accessibility and calls to action.
A website is a product people use, so another person needs to test it.
The website should combine the founder concept, line-up, location/travel information and brand without becoming cluttered.
Build the festival site in an approved website builder with functional navigation.
Code the site and test links, readability and responsive behaviour.
Create an interactive prototype where a tester can complete the same key visitor tasks.
The final challenge is the launch: present the product, gather feedback and decide what to improve next.
Which page was hardest to design well?
What did a tester notice that you did not?
How could AI help maintain or personalise a festival website without reducing accessibility or trust?
Your Step 5 output is the main evidence. Keep to the stated size or time limit.
Choose Your Tools
Use the tools available to you. The quality of the thinking, research and audience experience matters more than a particular app.
Use a school-approved website builder, Google Sites, WordPress, HTML/CSS or another appropriate tool.
Use a site map and simple wireframes before building. Prioritise visitor tasks: line-up, tickets, travel, accessibility and key information.
Test navigation, mobile readability, contrast, alt text, headings and clarity with another user.
Your Step 5 output is the main evidence. Keep to the stated size or time limit.
Choose Your Tools
Use the tools available to you. The quality of the thinking, research and audience experience matters more than a particular app.
Use a school-approved website builder, Google Sites, WordPress, HTML/CSS or another appropriate tool.
Use a site map and simple wireframes before building. Prioritise visitor tasks: line-up, tickets, travel, accessibility and key information.
Test navigation, mobile readability, contrast, alt text, headings and clarity with another user.
Choose Your Tools
Use the tools available to you. The quality of the thinking, research and audience experience matters more than a particular app.
Use a school-approved website builder, Google Sites, WordPress, HTML/CSS or another appropriate tool.
Use a site map and simple wireframes before building. Prioritise visitor tasks: line-up, tickets, travel, accessibility and key information.
Test navigation, mobile readability, contrast, alt text, headings and clarity with another user.