Adjustment for multilingual support

hunvreus commented 7 years ago

This ticket is broken in 2 parts. Only act on the first one for now;

[ ] Test that all translated content is in the {lang/} subfolder; I can't remember for example if we store the posts in zh/_posts or _posts/zh (for example with Chinese). It should be zh/_posts.
[ ] (OPTIONAL) Renamed lang attribute and rely on subfolder; I did some more testing over the weekend and I think the best and most flexible approach is to use the subfolder to specify the language. That means the yaml front matter should omit lang: zh for example, and rely on the fact that the entry is in the zh/ subfolder or has an explicit category: zh attribute. I understand this may break a bunch of things (like the translation links in the edit form) so hold off for now if it's more work than 10 to 20 minutes. We probably need to discuss it a bit more anyway.

hunvreus commented 7 years ago

By the way, the site we're gonna be testing it against is at https://github.com/Wiredcraft/1912pike.

zbal commented 7 years ago

JuhaS commented 7 years ago

@hunvreus can this be closed, I believed we used another approach in the end.

JuhaS commented 7 years ago

You can safely ignore the stuff above.

However;

When the language is not default, you need to save the language as categories: in the YAML front matter as well. For example;
```
title: Non default language post
lang: en
categories: en
```
If a post has no translation yet, we should allow the use to change the language and have the language bar enabled.

Wiredcraft / jekyllpro-cms