That brief — simple, warm, real — became my design compass for the whole project.

Before I opened Figma, I spent time understanding the space. I audited competitor school websites and reviewed what parents were actually saying online.

I looked at eight school websites near Chikkalasandra and a few broader Bengaluru schools. Here's what I found:

I sat with the founder and principal and asked them things they didn't expect to find in a design brief:

• "What do kids feel like on their first day?"
• "What do parents say when they come back years later?"
• "What makes SVS different — in one sentence, no marketing language?"

The answer that stuck with me:

That became the emotional brief. A school where every child is seen. The design had to feel like that.

A note on receipts: These three are synthesised from the founder & principal's 26 years of admissions conversations, the competitor audit, and Google Maps reviews of nearby schools.

Before designing a single screen, I mapped out the structure.

SVS's content fell naturally into one scrollable homepage with three deep-dive overlays. Parents shouldn't have to navigate. They should discover as they scroll.

One month. One designer. One client who wanted simple. I used a 2×2 Impact vs Effort matrix with urgency as a third dimension — bigger bubble = more urgent for the admissions deadline.

The list I cut was as important as the list I kept. Here's the reasoning, not just a list:

What that meant in practice:

• Festival photos from their own events, not stock images
• Actual student events (Krishna Janmashtami, Christmas, Republic Day)
• Copy that sounds like a person, not a press release
• Colours that have energy, not just "trustworthy navy"
• Typography friendly on desktop, formal on mobile
• Small personality details parents notice and feel — even if they can't name them

Every colour earns its place. Every combination passes WCAG AA — most pass AAA.

Anyone can build a school website. The difference is the small stuff — the moments that make a parent stop and feel this isn't a brochure, this is an actual place where my kid would go.

Six sections, one scrolling page — each with its own personality, all sharing the same design DNA. Toggle below to compare the final build against the lo-fi wireframes.

After the first major build (hero, our story, academics, basic nav), I shared it with the client. Their reaction:

That one sentence told me the direction was right. The warmth, the colour, the real photos — they felt the difference from the corporate competitors immediately.

What they asked to change after iteration 1:

• The admissions banner needed to be more gentle — the first version felt too shouty
• The "Our Story" section needed more breathing room
• A few copy lines felt too formal — they wanted simpler, conversational language
• On mobile, the heading font felt too heavy — wanted professional, not childlike

What I changed:

Each round of client feedback made the design better. The client knew what they wanted — they just needed something to react to. That's what iteration is for.

No case study is honest without the messy bits. Here are the ones that mattered — shown the way they felt.

Mid-April 2026. The site went live before admissions opened. I gave the client a one-page handoff: how to update text, how to swap photos, how to connect Google Search Console.

Already discussed with the client for summer/autumn 2026:

• Faculty profiles + teacher messages (photo shoots over summer)
• Principal's welcome video on the hero
• Annual results page (after Class 10 results 2026)
• Events calendar
• Expanded gallery sorted by year + event
• Alumni section. there are stories worth telling.

The architecture is already ready. The design system has room. The codebase is clean enough to extend.

Known issues I'm fixing.