An unfamiliar service journey
Visitors need to understand what happens before deciding whether to enquire.
Mars Naadi / Website study
Make the process clear.
In either language.
A bilingual website build for a palm-leaf astrology practice, focused on explaining the consultation process and carrying the experience across English and Tamil.
- My contribution
- Website design, responsive build and localisation
- Timeline
- 2026
- Status
- Working website build · Launch unconfirmed
Treat language as part of the experience
English and Tamil versions share the same page structure, with language choice retained.
A bilingual responsive build
The site includes the process, reading formats, FAQ and currency switching.
01 / Explain before asking
The sequence needs to answer “what happens next?”
The page moves from an introduction into the consultation process, what the visitor receives, reading formats and frequently asked questions. That sequence gives a new visitor practical context before the contact step.
The visual direction uses a manuscript-inspired palette and serif headings, with a practitioner photograph anchoring the lineage section. The portfolio case focuses on communication and localisation; it does not make claims about the service’s predictive accuracy.
- 01Orientation
Introduce the practice.
- 02Process
Explain the sequence.
- 03Formats
Clarify the available readings.
- 04Questions
Resolve uncertainty before contact.
02 / Design across languages
A language switch is more than a translated heading.
The implementation carries translatable content through a shared page structure. English and Tamil are available from the header and the mobile navigation, and the language choice is remembered on the device.
Tamil uses its own supporting typeface. That gives the writing system a deliberate typographic treatment instead of relying on an incidental fallback. The mobile layout also needs to accommodate changes in text length.
The reading cards include an independent USD/INR display switch. Those are supplied price values, not a live currency conversion. Language preference and currency preference remain separate choices.
One content structure
The same sections and reading order exist in either language, so the visitor does not enter a smaller translated version of the site.
Remember the preference
Persist the selected language and currency locally so the visitor does not repeatedly make the same choice.
Make the control reachable
Keep the language action available in the compact navigation, alongside the mobile menu.
Respect reading needs
Use visible focus, a skip link and reduced-motion handling around the shared content.
From the actual website buildOpen excerpt ↗
03 / Separate build from launch
The implemented experience is the evidence.
The site is built as static HTML, CSS and JavaScript, with a responsive menu, FAQ, language switching and currency display. It can be handed over without requiring an application server.
Launch still depends on verifying contact details, replacing sample testimonial copy and completing the legal destinations. This case describes the working design and implementation, without presenting those sample claims as validated evidence.
What the work achieved
A considered localisation build.
The project brings content structure, Tamil typography, persisted preferences and responsive behaviour into one website. Usability and business outcomes have not been measured.
Website design and AI-assisted implementation: Sivabalan M. Practitioner photography supplied with the project. Language and currency behaviour are implementation evidence; service outcomes are not evaluated here.
Next project