QUEST Book
South Asia’s large-scale AI & STEAM quiz platform — school registration, season sites, syllabus/rules, and admin tooling for QUEST seasons through 2026.
Season operating flow
Recruit schools → explain AI & STEAM → register → run the season.
- Recruit School discovery
- Explain AI & STEAM story
- Register School intake
- Syllabus PDF rules
- Compete Season stages
- Relay EDUACE pathways
The challenge
QUEST is a multi-city, multi-school competition with classroom prelims, regional finales, and a national stage. The digital layer has to recruit schools, explain AI & STEAM framing, and support season logistics without collapsing into a static microsite.
Earlier seasons proved the brand; newer seasons needed sharper AI narrative, cleaner registration UX, and maintainable PHP surfaces for annual relaunches.
School decision-makers and students need different energy on the same platform — credibility and logistics for one, clarity and pathways for the other.
What we built
We built and refreshed QUEST web properties (quest / quest_2025) with season-aware about, FAQ, contact, school registration, and asset systems — including syllabus and rules distribution for QUEST 2026 Season 04.
Admin/school tooling companions support the operational backbone behind the public story.
Season relaunches reuse a battle-tested PHP structure so content, PDFs, and registration can update without rewriting the product each year.
Platform architecture
Season sites, school registration, syllabus/rules, and admin companions.
Season public web
About, FAQ, contact, and AI & STEAM narrative.
School registration
Institution intake for multi-city seasons.
Syllabus & rules
PDF distribution embedded in the product.
Admin companions
Operational tooling behind the public season story.
QUEST season diagram
How brand, registration, and academic AI strands run as one annual system.
Schools
Season
Ecosystem
Public pages never expose raw school rosters — ops graphs stay internal.
Design principles
QUEST is not a generic quiz — AI literacy is competition design, not a badge.
AI is curriculum
Literacy is designed into rounds — not a marketing sticker.
Two audiences
Schools need credibility; students need energy and clarity.
Relaunch without rewrite
Season architecture must survive annual packaging.
Private ops graphs
Registration data fuels intelligence internally, not public dumps.
How we approached it
Positioning led build decisions. QUEST is not a generic quiz; it celebrates India’s STEAM legacy while forcing an AI literacy thread through competition design.
We designed pages for two audiences simultaneously: school decision-makers (credibility, association with Amrita, logistics) and students (energy, clarity, pathways).
Season relaunches reuse a battle-tested PHP structure so content, PDFs, and registration can update without rewriting the product each year.
Visual systems (logo marks, about photography, brand tiles) stay consistent so QUEST compounds recognition across seasons.
Evergreen brand story stays separated from season facts so updates cannot accidentally break logistics pages.
Where AI enters — and where it must not
AI is embedded in the academic product: syllabus and round design emphasize AI concepts alongside STEAM.
Digitally, registration and school data create a competition graph — valuable for future AI features like school readiness scoring, practice recommendations, and anomaly checks on bulk enrolments.
Content architecture separates evergreen brand story from season facts so AI-assisted content updates can happen safely without breaking SEO or logistics pages.
The long game is a feedback loop: competition performance data informing Magic of Skills / Campus Coach pathways inside the broader EDUACE ecosystem.
Technical notes from production
Details that only show up once the season is real.
- Season relaunches reuse PHP structure so annual content and PDFs update without product rewrites.
- Evergreen brand story is separated from season facts to protect logistics pages during content edits.
- School registration creates a competition graph usable later for readiness and anomaly features — not published as open data.
- Brand asset centralization keeps recognition compounding across seasons.
Delivery & systems
PHP season sites with modern front-end styling, PDF syllabus/rules delivery, school registration, and admin companions.
Brand assets centralized so QUEST identity stays coherent from favicon to finale stage creative.
Season 04 (2026) packaging for syllabus/rules distribution inside the site.
Stack
Click a layer — each one maps to a real season responsibility.
Season sites
PHP
Public QUEST properties for annual competition cycles.
Brand assets from the live product
Primary mark pulled from the Olympiad codebase — shown once, on the surface it was built for.
Outcomes
- Season-ready QUEST 2026 public platform
- School registration and FAQ/support surfaces
- Syllabus & rules distribution built into the site
- Reusable architecture for annual relaunches
- Competition graph ready for EDUACE AI pathways