Build blueprint
The decisions behind the UI — with real examples.
Switch tabs to see what we built and why it works for this specific domain.
Examples
Timeline narrative
Scannable milestones build credibility fast.
Education
St. Stephen’s, DU gold medal.
Civil service
IA&AS, Principal AG roles.
Parliament
Committees, Sansad Ratna Award 2022.
Context
Who it’s for, and what changed.
Users
Constraints
Problem
The friction we removed.
Needed an authoritative public profile that communicates governance credibility quickly: a clear mission statement, a verifiable timeline (education → civil service → parliament → BJP), and structured public impact content.
Outcomes
- Clear timeline narrative with scannable milestones
- Proof-driven layout using metrics and recognitions
- Structured modules ready for ongoing content (questions, committee work, advocacy)
Solution
The approach.
A story-driven profile: strong hero mission, metric strip, stepwise timeline cards, role-based sections, parliamentary work/media embeds, and clear CTAs for feedback/volunteering/collaboration.
Build notes
- Content-first layout decisions
- Mobile readability prioritized
- Consistent component patterns
UX patterns
Design decisions that scale.
These patterns make the experience predictable under stress—whether it’s content discovery or day‑to‑day ops.
- Mission-first hero with dual CTAs
- Metric strip for credibility (service years, contributions, engagements)
- Timeline narrative blocks (education → service → parliament → present)
- Tabbed/sectioned content for parliamentary work + committees + advocacy
- CTA stack for feedback, volunteering, and media collaborations
Typography
Readable = credible.
Geist (Sans) with calm hierarchy
Supports an authoritative tone while keeping content accessible on all devices.
UI system
Color + spacing discipline.
Deep navy/ink tones with restrained accents to keep the experience credible and focused.
Screenshots
What shipped.
Click to zoom.
Next
What we’d do next.
Tighten the workflow
Audit friction points and reduce steps for the key conversion/ops paths.
Make the system faster
Performance budgets, image strategy, and key-path caching for speed.
Scale with a design system
Tokenize spacing/type, build reusable components, prevent drift.
Start a conversation
Ready to talk about your next release?
Share where your product is today and where it needs to be in the next 6–12 months. We'll respond with a thoughtful point of view—not a canned pitch.
- 01
Share context
Where you are and what’s next
- 02
Get a point of view
Ideas, risks, and options
- 03
Shape the engagement
Scope, squad, and timeline
- Reply within 1–2 business days
- No generic sales deck
- NDA available on request
Prefer email? Use our contact page · hello@simegh.com
Project brief
~2 minutes · we read every submission