You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
No need of site-wide internationalisation (i18n). It's okay if "Home", etc. in menu are called "Home" in any language.
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.
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.
Thus, no restriction on which post should be translated into which langauge first.
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: