+ [2016-10-08T21:52:31Z] Ademan osfameron: hrm that's a very interesting idea, thanks. For the moment I've semi-required duplication, each translated page is a stub with front matter declaring the language, and an include_relative to the "base" page... seems like it'll work but I haven't fleshed it out completely yet
+ [2016-10-08T21:53:10Z] Ademan a symlink might be a huge improvement though, not certain if that'll fly on github pages (is git aware of symlinks?) but it's worth a shot
+ [2016-10-08T22:01:24Z] osfameron not sure, not tried, but let us know *if* it works :D
+ [2016-10-08T22:01:31Z] osfameron I suspect that duplication is the way to go though tbh
+ [2016-10-08T22:02:11Z] osfameron but I've not done i18n with jekyll personally, there may be better practices

message no. 152971

Posted by Ademan in #jekyll at 2016-10-08T20:14:06Z

basically foo.html/foo.md -> foo.en.html, foo.de.html, ...
+ [2016-10-09T07:50:22Z] gynter Ademan: https://github.com/gynter/gynter.github.io
+ [2016-10-09T07:50:23Z] jekyllrb Title: GitHub - gynter/gynter.github.io: Homepage of Günter Kits (at github.com)
+ [2016-10-09T07:51:25Z] gynter This explains it a bit: https://talk.jekyllrb.com/t/two-languages-on-the-same-site-how-to-disadvantages/1150
+ [2016-10-09T07:51:26Z] jekyllrb Title: Two languages on the same site: how to? Disadvantages? - Help - Jekyll Talk (at talk.jekyllrb.com)
+ [2016-10-09T07:51:47Z] gynter https://talk.jekyllrb.com/t/two-languages-on-the-same-site-how-to-disadvantages/1150/2?u=gynter