Add i18n

[tcarreira]

Feature translations with Hugo i18n capabilities.

Currently:

• English (default)
• Portuguese

The default English text should be just the same.
It will be easier for Portuguese readers if you add DefaultContentLanguage = "pt" on your config.toml file

[tcarreira]

Oops, too soon.
This PR is not ready yet, I'm sorry.

I'll work on this later, I'm closing this PR for now

[onweru]

Thanks @tcarreira for contributing.

This PR is not ready yet, I'm sorry.

I figured and was hesitant to merge. Looking forward to what you come up with. Thanks again.

[razonyang]

Hi @tcarreira, any news on this? I'm considering implementing I18N for my site based on this.

[tcarreira]

Hi @razonyang
I believe the previous commit is enough for the theme, but I intend to get a decent PR on it, this week.
I want to write some documentation/examples so others don't get stuck as I did.

But I would be glad if you help me with a thing: does the configTaxo.toml serve any purpose?
because:

• I was really confused on translating the taxonomies (tags, categories, etc...)
• it turns out, it is really simple, just call the taxonomies with the correct translation, but...
• taxonomies had to be declared on the config.toml, not on the configTaxo.toml, as they are in the example.

[onweru]

But I would be glad if you help me with a thing: does the configTaxo.toml serve any purpose?

Good question @tcarreira. We included that file only as a part of this guideline. I can guarantee that it's not used by the theme. So, I reckon you wouldn't need to consider it in your PR.

I want to write some documentation/examples so others don't get stuck as I did.

😎 👏

[tcarreira]

Hi @razonyang. Have you seen #39 ?

[razonyang]

@tcarreira I haven't noticed this PR yet, I'll try it tonight.