Localization: first class citizen
- Dominant language
- Elixir
- Stars
- 1.3k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am not sure if you have already tackled this topic: translations.
The world has seen some CMSs in the past where the ability to translate things was just added later via plugins etc., which quite often resulted in clumsy development experience (e.g. interop with other addons etc.) and UX for the content authors.
For sure there are others which integrate translatable content very well.
I just wanted to wake your awareness on this topic, because I believe it will be useful feature.
Cheers
Contributor guide
Research direction
Start by reviewing the Beacon CMS content model and its Phoenix LiveView authoring flow to determine where translated content would belong. The issue provides no files, tests, or entry points and does not define supported languages, translation behavior, or acceptance criteria; the work is not ready to begin without a design discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- content, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100