Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Jinja2 Support for Pydgeot

Add support for Jinja2 templates to Pydgeot. Any changes to extended or included templates will propagate regeneration to the file that used those templates. Templates may set context variables that are accessible from other templates, which will also affect the regeneration.


  • Standard Jinja2 templating.
  • Globally available context variables.
  • Regenerate files dependent on other templates or context variables.



Via pip:

pip install pydgeot_jinja

Or via source:

git clone pydgeot_jinja
cd pydgeot_jinja
python install


Add jinja to your pydgeot.conf plugins list to enable the plugin. Then add jinja to the processors list in pydgeot.conf, or nested .pydgeot.conf's, to use the file processor. Options are, also, placed under a jinja key.

  • source_ext Extension of source files to build. Default: .html
  • build_ext Extension of built files. Default: .html
  "plugins": ["jinja"],
  "processors": ["jinja"],
  "jinja" {
    "source_ext": ".jinja"


The Jinja2 plugin will process any .html (or source_ext extension specified in pydgeot.conf) file as a Jinja2 template.

A page may be marked as template only by setting the template_only variable to True. This will cause the file to not be generated, but any changes will still cause dependent files to be generated.

Context Variables

Setting a context variable makes it available to the file it was created in, and to any other template file. {% setcontext name="value" }%

Context variables can be accessed in the setting file (or extended and included files,) in the same way as if it had been created with the standard Jinja set.

Context variables may be created with the same names across multiple sources, so global access is done iteratively. getcontexts(name, "value") will retrieve a list of files that have set a context variable matching the name and value. The value may be a glob pattern.

For example, {% for page in getcontexts("fullname", "test.*") %} would find any file with context variables named "fullname" with values starting with "test.", then grab all of that files context variables and set them as properties of page.


No description, website, or topics provided.




You can’t perform that action at this time.