Support localization for the DoEKS website
- Dominant language
- Shell
- Stars
- 857
- Forks
- 303
- Avg merge
- 11h 5m
- Merged PRs (30d)
- 3
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
#### What is the outcome that you are trying to reach?
I would like to see the DoEKS website support localization and let the users adopt the DoEKS with their familar language.
#### Describe the solution you would like
localization support
#### Describe alternatives you have considered
#### Additional context
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the DoEKS website content and its current delivery structure, then define supported languages and how users select them; done means the website can be used in the agreed localized languages.
Written by the indexing model from the issue text.
Assessment
- Domain
- localization, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100