Skip to content
This repository has been archived by the owner on Mar 2, 2022. It is now read-only.

Should we allow localized content? #3

Open
saranshkataria opened this issue Sep 12, 2019 · 6 comments
Open

Should we allow localized content? #3

saranshkataria opened this issue Sep 12, 2019 · 6 comments

Comments

@saranshkataria
Copy link
Contributor

Though it is a great feature to have, but this list is going to be a huge one, and having localized content included in it would increase this list to a very long one as well. My opinion is maybe have a separate list for localized content and not have it in here.

@tvalentius
Copy link
Contributor

Great suggestion @saranshkataria !

For now, let's see how big this list are going to be.
Since, it will be very easy and straight forward to create a separated .MD file within this repository

I do think it make sense to have a localized content in the near future if the list is becoming very huge.

Cheers!

@alicerp
Copy link
Contributor

alicerp commented Apr 23, 2020

Would it make sense to create multiple branches in the repo in this case?

@aboullaite
Copy link
Contributor

@alicerp I prefer having folders, for each specific language and keep everything in the master branch

@saranshkataria
Copy link
Contributor Author

I agree with @aboullaite, though I think a file name with the language name in the name of the markdown file instead of having another folder would be sufficient.

@AJV009
Copy link
Contributor

AJV009 commented Jul 18, 2020

So am I allowed to add (PR) our developer circle member blogs and articles links to this file?

@Bello2609
Copy link

@aboullaite it will be nice if each languages have their own folder for easy navigation

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants