-
-
Notifications
You must be signed in to change notification settings - Fork 131
Localize comment in HTML #225
Comments
+1. Wrote out an entire message suggesting to link to the localized repo's page instead of the main repo, then saw that you had already written that. Oops. Anyway, I think linking to the localized repo is a good idea. Something we probably want to leave up to the localization teams is if they want to include both the English and localized versions, if they think they might also have a decent English-speaking readership as well (as I know some do). That way, people who can contribute to this repo, without a language barrier in the way, are able to if they'd like to. |
+1 the "localizations" shouldn't just be translations but should actually include additional content and pointers relevant to that language community. |
+1 we need to add this into the build process. When I originally built it, I thought we'd only be handling text content, and built to that spec. This is another use case that might be good to implement a different templating engine like jade or handlebars. |
Haha, I think this specific line landed as a result of my needing an "invisible change" when we were needing to do a test deploy of the website project. Anyway, ya, eventually the template solution will probably need a bit more flexibility. My actually answer to this is: eventually I'd like every page to have an "edit/contribute/make this page better" type link on it which points right to the Markdown file in the related repo. Re: translations, we could maybe do something like: |
See #257 for this |
Closing as #257 has landed. |
There's a HTML comment on every page:
<!-- See something you like? Want to help? Visit https://github.com/iojs/website to contribute -->
Currently this comment is kept as is on every localised version. Might be nice to have this comment translated too, and perhaps a link to the relevant localisation repo.
The text was updated successfully, but these errors were encountered: