Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localize i18n and Refactor Content folder structure #17

Open
ManasMadrecha opened this issue Jul 2, 2021 · 0 comments
Open

Localize i18n and Refactor Content folder structure #17

ManasMadrecha opened this issue Jul 2, 2021 · 0 comments

Comments

@ManasMadrecha
Copy link
Member

Currently, Aagam are stored in language specific folders like en, hi, etc. While this categorisation is logical, it makes it hard to add a whole new language unless that language has some substantial content added into it.

Proposal

  1. No need of site-wide internationalisation (i18n). It's okay if "Home", etc. in menu are called "Home" in any language.
  2. Create i18n for each post. This way we can add n number of translations to each individual post irrespective of whether that post's parent or children has translation. This drastically speeds up content updation.
  3. Each post should be in a seperate folder and that folder will contain the translations, including English and original content. Any person can just pick up a folder and begin translating easily into any language he or she wants.
  4. Thus, no restriction on which post should be translated into which langauge first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant