Localize i18n and Refactor Content folder structure

[CA Manas Madrecha]

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.