Skip to content

Story 036: Multi-Language Support #36

@iagocavalcante

Description

@iagocavalcante

Summary

As an organizer, I want the platform available in multiple languages, so that attendees and organizers can use it in their preferred language

Blocked by: (none)

Acceptance Criteria

1. Platform Localization

  1. Language Selection: Users can select their preferred language. Platform auto-detects preference from browser settings.
  2. Initial Languages: Platform ships with Portuguese (BR) and English.

2. Event Content Translation

  1. Translatable Content: Organizers can provide translations for event content (names, descriptions, custom questions) in multiple languages. Untranslated content falls back to the default language.

Test Plan

Tier 1 — Acceptance Tests

  • AC1: Select preferred language and auto-detect from browser settings
  • AC2: Platform fully available in Portuguese (BR) and English
  • AC3: Organizer provides event content translations with fallback

Tier 2 — Edge Cases

  • Switch language mid-session preserves cart and progress
  • Event with partial translations falls back per field
  • Unsupported language falls back to default
  • Email templates sent in user's preferred language

Assumptions

  • Adding a new language requires adding translation files only -- no code changes.
  • Community-contributed translations accepted via pull requests.

📄 Full spec: spec/elixir-phoenix-migration/10-product/stories/story-036-multi-language-support.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentic-workflowStory generated via agentic workflow

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions