Redesign for better Multilanguage about betterspecs HOT 7 CLOSED

i think it should be redesigned for a better multilanguage site.

When the original english version is changed then all translations for this spec should be marked somehow.

Just now it can be out of sync if something chaned / added

from betterspecs.

Copypaste from the issue #66

• Layout must be DRY and reusable.
• Menu items must be auto-generated from headers instead of being inserted manualy.
• Same with social buttons.
• Same with additional info links.
• Translations should be more maintanable. It will be great if the translation maintainer could receive a letter when some practice was added or changed in original version of the betterspecs.
• Practices should be voted and discussed on the site, not on the github.

from betterspecs.

hi @killthekitten , is this what you are looking for? https://www.transifex.com/

from betterspecs.

@shunwen looks good, thanks

from betterspecs.

Thanks @muescha for opening this much needed ticket. I would love to see if out there already exists something similar to what we need. Even more, the new version of better specs, in my ming should do mainly two things.

• Easily update translations when a change is made
• Multi programming language, which means to have the ability to define better specs for ruby, but also for Node, Python and so on.

About the initial points of this issue, I'm fine with everything, out of the last one. I mean, it's ok to discuss in the site, but we'll have to take all existing comments to the new version. This is important.

from betterspecs.

I would like to update everyone by taking a look at this comment I made on another issue:

@onebree said in #65 (comment)

When we change the format of the site, we can haven links to the country flag, which points the user to a translated version of the site. This is why Pages would be good, because it will be easier to format other languages (using ** for bold) and to render partials dependent on a parameter passed to the URL (like [language]=de)

Basically, I plan to overhaul the site and move it to Github Pages with Jekyll, where we can edit content with Markdown. This will make it much easier to read (as Github renders markdown), view changes, and organize views.

from betterspecs.

this seems to have been achieved overall now that we're not doing translations anymore. 🙂

from betterspecs.