Support for translations about webdesignerschecklist

[grayghostvisuals]

Would you be interested in receive translations?

If you're asking “Am I interested in translating this for other languages” then yes, yes I would be.

I believe we have some ways to do it. Maybe using a template engine or simply by generating other files like index-ptbr.html, index-de.html etc.

That's a great idea, although we do translations with the Accessibility Project using Google Translate which you can see in the footer of the site http://a11yproject.com.

[handrus]

I am offering myself to translate it, at least to portuguese and spanish.
Just need some guidance as how would you prefer it ti happen. Maybe something like https://github.com/zaach/jsxgettext or http://lostechies.com/gabrielschenker/2014/02/11/angularjspart-12-multi-language-support/ could make it incredibly easy for anyone to translate it to other languages.
since google is improving but is far from being acceptable (IMHO).

[grayghostvisuals]

I'm not partial so whatever you think is best and can work within the flow here then whatever you decide on is fine by me :)

I would make yourself a sep. branch called…wait for it…“translations.”

Thanks for donating your time to this feature. It's gonna rock!

[diagramatics]

Or you guys can do what mdo/code-guide does. Translators can fork the repo, translate it, and open a PR to add the link to the translated fork on the readme.

I might jump into the fray as well.

[grayghostvisuals]

@diagramatics
I personally don't care to maintain multiple languages so anything that's easy for me to maintain will be my choice, otherwise I'd rather see other forks to translate as needed.

[grayghostvisuals]

Is this issue really needed anymore? I'd like to close it as it seems not really interesting to anyone to finish let alone begin working on.