Age | Commit message (Collapse) | Author |
|
It is out of sync with reality, has some disabled tests, and the cost
of getting it up-to-date is too high to be worth it.
|
|
And pull up common member vars like Tmpl and Multilinguage.
Or: the final multilingual TODO-fixes.
See #2309
|
|
Implements:
* support to render:
* content/post/whatever.en.md to /en/2015/12/22/whatever/index.html
* content/post/whatever.fr.md to /fr/2015/12/22/whatever/index.html
* gets enabled when `Multilingual:` is specified in config.
* support having language switchers in templates, that know
where the translated page is (with .Page.Translations)
(when you're on /en/about/, you can have a "Francais" link pointing to
/fr/a-propos/)
* all translations are in the `.Page.Translations` map, including the current one.
* easily tweak themes to support Multilingual mode
* renders in a single swift, no need for two config files.
Adds a couple of variables useful for multilingual sites
Adds documentation (content/multilingual.md)
Added language prefixing for all URL generation/permalinking see in the
code base.
Implements i18n. Leverages the great github.com/nicksnyder/go-i18n lib.. thanks Nick.
* Adds "i18n" and "T" template functions..
|
|
See #2014
|
|
These are of no interest outside the package.
|
|
See #1646
|
|
And at the same time rename and unexport the badly named `Layout()` func. That method is not very usable outside the package.
Fixes #1539
|
|
|
|
extension option.
|
|
The render code path would use a fallback if there was an exception.
This change instead relies on explicit declaration of the layout to use
and includes a check to see if the layout indeed exists before
attempting to render it.
|
|
Moved the generation of the target path to the page breaking all
dependecies on Site.
|
|
Allow content that is not markdown and does not need to be rendered to
exists in the content directory. Currently any valid html or xml
document can exist. Templates are applied to these documents as well.
If you need to have content that doesn't have templates or AbsUrlify
like operations, then continue to put this content in static and it will
be copied over.
|
|
|
|
Now reports if the page will be rendered or not and by which render
engine.
|
|
|
|
This provides an abstraction over how files are processed by Hugo. This
allows for alternatives like CMS systems or Dropbox, etc.
|
|
|
|
Translate handles Ugly Urls.
|
|
|
|
|