Command Palette

Search for a command to run...

Case studyPublic serviceMay 2026

தமிழ்நாடு அரசு இணையதளத்தை குடிமக்கள் சேவை தளமாக மறுவடிவமைத்தல்.

Redesigning tn.gov.in as a modern citizen-service platform.

The old TN Gov concept was too close to a visual reskin. This update reframes it as a full service experience: search-first, Tamil-ready, AI-assisted, mobile-friendly, and built from Tamil DS components.

தமிழ்நாடு அரசு சேவைகள்

Tamil Nadu Services

மாதிரி / Prototype

தேடல் வழி அணுகல் / Search-first

திட்டங்கள், சான்றிதழ்கள் மற்றும் சேவைகளை எளிதாகக் கண்டறியுங்கள்.

வருமான சான்றிதழ், பட்டா, ஓய்வூதியம்...

சான்றிதழ்கள்

Certificates

திட்டங்கள்

Schemes

மாவட்டங்கள்

Districts

குரல் AI / Kural AI

தேவையான ஆவணங்கள், தகுதி மற்றும் விண்ணப்ப நிலையை அறியக் கேட்கவும்.

வருமான சான்றிதழுக்கு என்ன ஆவணங்கள் வேண்டும்?
ஆதார், முகவரி சான்று மற்றும் வருமான ஆதாரங்களை தயார் நிலையில் வைத்திருக்கவும்.

This is an unsolicited educational redesign by Tamil DS. It is not affiliated with, endorsed by, or commissioned by the Government of Tamil Nadu.

450+

Service paths

Structured around citizen jobs instead of departments.

6

Navigation groups

Reduced top-level decisions with clearer hierarchy.

AI

Guided support

Kural AI explains documents, eligibility, and next steps.

AA

Quality target

Contrast, focus, mobile sizing, and Tamil readability.

01 / Audit

The redesign starts from service friction.

The current portal has valuable information, but the interface makes citizens work too hard before they can act.

Discovery is department-first

  • Citizens need task language like certificates, pensions, and status.
  • Important services compete with announcements and administrative links.
  • Search does not feel like the main way to move through the site.

Mobile experience feels secondary

  • Large navigation structures are hard to scan on small screens.
  • Touch targets and section density create unnecessary effort.
  • Key flows need clearer vertical rhythm and fixed action hierarchy.

Support is passive

  • Users who do not know document requirements need guided help.
  • A modern government portal should answer common service questions inline.
  • The chat entry point must be calm, persistent, and trustworthy.

Visual hierarchy is inconsistent

  • Cards, tables, carousels, and announcements lack one shared anatomy.
  • The redesign needs fewer surfaces, more white space, and stronger type scale.
  • Tamil and English content must align cleanly without crowding.

02 / Direction

A SaaS-quality public-service interface.

The redesign follows Tamil DS quality standards: generous white space, restrained card usage, clear metrics display, subtle grid backgrounds, and decisive action surfaces.

Search becomes the primary action

The redesign starts with service discovery because most citizens arrive with a task, not a department name.

Service cards replace dense link lists

Every repeated service pattern is a clear card with hierarchy, status, and a single obvious movement path.

Kural AI is built into the journey

AI guidance appears as both a dedicated section and a persistent floating support widget, designed to stay reachable throughout the service journey.

Accessibility is a visible quality bar

Focus states, contrast, Tamil readability, mobile touch targets, and reduced clutter are treated as design requirements.

03 / Information architecture

Move from pages to citizen jobs.

The main structural change is not decorative. It changes how people understand what the government can do for them.

Before

Department links and mixed utility items in the primary navigation.

After

Six job-based groups: services, schemes, districts, documents, updates, and help.

Before

Search appears as a secondary utility.

After

Search is the hero action with quick prompts for high-demand services.

Before

Scheme lists require reading and interpretation.

After

Scheme cards show benefit, eligibility signal, documents, and apply action.

Before

Help content is separate from the service journey.

After

Kural AI stays available as a persistent floating assistant throughout the service journey.

04 / Component system

The case study now documents actual reusable pieces.

Every part of the block should read like Tamil DS, not like a one-off landing page.

Component
Hero searchPrimary service discoveryLarge input, clear prompt chips, no decorative clutter.
Service cardsRepeatable category accessOne action path, consistent icon container, hover feedback.
Scheme cardsEligibility and benefitsBenefit data first, CTA grouped in footer, no overloaded actions.
News cardsOfficial updatesDate, type, summary, and single read action.
Kural AI panelGuided supportConversational surface, examples, sticky composer, calm floating trigger.
Typography safetyBilingual text renderingAuto-scaled line heights (leading-snug), min-h-* padding bounds, no diacritic clipping.
FooterTrust and legal closureDense but organized links, not a second homepage.

05 / AI layer

Kural AI is part of the service design, not a novelty.

The assistant is designed around practical government questions: eligibility, documents, status, office location, and next steps.

Suggested prompts

The widget opens with useful questions so citizens do not need to know how to phrase a query.

Persistent launcher

A bottom-right trigger keeps help visible without interrupting the page or blocking primary content.

Service-aware answers

The AI pattern is written to connect answers back to service cards, documents, and application paths.

06 / Delivery checklist

What the finished page must prove.

This is the acceptance bar for the TN Gov redesign and the page that explains it.

Meets the Tamil DS quality bar for layout, spacing, typography, and component usage.
Uses Tamil DS primitives and shared component anatomy.
Keeps cards flat, spacious, and never nested inside decorative cards.
Uses subtle checked-grid preview backgrounds only where they support examples.
Aligns Tamil and English content with enough line-height and whitespace.
Uses automatic line-height auto-scaling for Tamil text to prevent diacritic overlap.
Avoids fixed-height containers with overflow-hidden on text nodes to prevent vowel marker clipping.
Keeps the floating chat widget usable on mobile and desktop.
Shows concrete service outcomes, not generic government marketing.
Documents the educational and non-affiliation disclaimer clearly.
Case study updated to the new visual direction

The prototype and story now speak the same language.

The case study now supports the redesigned TN Gov block with a cleaner narrative, component-level decisions, and a practical checklist for continuing the full system refresh.