32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
## Purpose
|
|
|
|
Canonical specification for language-preference-persistence requirements synced from OpenSpec change deltas.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Landing page provides language selector
|
|
The system SHALL display a language selector on the landing page that allows switching between English, Tamil, and Malayalam content views.
|
|
|
|
#### Scenario: User selects language from landing page
|
|
- **WHEN** a user chooses Tamil or Malayalam from the language selector
|
|
- **THEN** hero and feed content update to requested language-aware rendering
|
|
- **AND** subsequent API requests use the selected language context
|
|
|
|
#### Scenario: User switches back to English
|
|
- **WHEN** a user selects English in the language selector
|
|
- **THEN** content renders in English
|
|
- **AND** language state updates immediately in the frontend view
|
|
|
|
### Requirement: User language preference is persisted and restored
|
|
The system SHALL persist selected language preference in client-side storage and restore it for returning users.
|
|
|
|
#### Scenario: Persist language selection
|
|
- **WHEN** a user selects a supported language on the landing page
|
|
- **THEN** the selected language code is stored in local storage or a client cookie
|
|
- **AND** the persisted value is used as preferred language for future visits on the same browser
|
|
|
|
#### Scenario: Restore preference on return visit
|
|
- **WHEN** a returning user opens the landing page
|
|
- **THEN** the system reads persisted language preference from client storage
|
|
- **AND** initializes the UI and content requests with that language by default
|