Support for i18n? about jekyll-theme-skinny-bones HOT 3 OPEN

There's no simple way to localize the theme. You basically have to modify a few of the layouts and includes anywhere a date is used to display on the correct format. It's far from automatic and you really have to know what you're looking for to fully localize it.

On one of my other themes someone forked it and created a localized version for one language. I think that's the way to go since it would next to impossible to keep the theme simple while trying to cater to a host of locales.

If you want to support posts/pages in multiple languages there are no "off the shelf" solutions I'm aware of. I've seen a few blog posts where people share how they went about doing it. But each of theme were fairly involved and can be intimidating for someone just starting with Jekyll. You're probably best looking at a full blown CMS that specializes in doing language variants.

Jekyll is one of those things that lets you do approach things in multiple ways. Which can be a blessing if you like to tinkerand build something from scratch, and a curse if you don't know where to start and are just learning.

from jekyll-theme-skinny-bones.

I have localized some hardcoded texts ("Overview", "Table of Contents", "Written by", "Updated") in my fork. Any interest that I submit this as pull request?
(see yonojoy@99f6616)

from jekyll-theme-skinny-bones.

@vperic
I tried different method about localisation my site/blog (WordPress & Jekyll) and always finish by having 2 differents sites, with the second language as a sub-domain for SEO reason.

from jekyll-theme-skinny-bones.