Skip to content

Commit

Permalink
Update documentation to clarify dependencies
Browse files Browse the repository at this point in the history
Closes getpelican#460, as it documents what needs to be done to be able to use the
theme. I tested the configuration recommended in the README in a minimal
test site without translations or subsite functionality.

Also removes `i18n.patch` that was accidentally committed to the repo.
  • Loading branch information
jranke committed Dec 22, 2016
1 parent a012bc3 commit 962c244
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 833 deletions.
10 changes: 9 additions & 1 deletion pelican-bootstrap3/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,15 @@ Point the `THEME` variable in your `pelicanconf.py` to

`JINJA_EXTENSIONS = ['jinja2.ext.i18n']`

to your Pelican configuration, as this template can be translated (see below).
to your Pelican configuration, as this template can be
translated (see `Translations` below). You also
need to activate a plugin that initializes the i18n jinja extension. One
possibility is an up to date version of the
[`i18n_subsites`](https://github.com/getpelican/pelican-plugins/tree/master/i18n_subsites)
plugin:

`PLUGIN_PATHS = ['/path/to/git/pelican-plugins']`
`PLUGINS = ['i18n_subsites']`

## Usage

Expand Down
Loading

0 comments on commit 962c244

Please sign in to comment.