About Template Engine Pug

Pug/Jade templates for the TemplateEngineFactory

Category 1Development Tools
Modules that have more to do with assisting development of a site rather than managing its content.
Category 2Markup Generation
Markup modules that are called upon to generate or parse markup (like HTML). Markup modules are most often used on the front-end of a site (rather than admin).
Release StateStable
Should be safe for use in production environments. *
Authordreerr
Module Version2.0.3
Class NameTemplateEnginePug
Compatibility2.7, 3.0
Date AddedMarch 1, 2017
Last UpdatedMarch 5, 2019
Recommended ByNew recommendations may take up to 1 day to appear.

Instructions

This module's files should be placed in /site/modules/TemplateEnginePug/
How to install or uninstall modules

README

TemplateEnginePug

License: MIT ProcessWire 3

A ProcessWire module adding Pug to the TemplateEngineFactory.

Requirements

  • ProcessWire 3.0 or newer
  • TemplateEngineFactory 2.0 or newer
  • PHP 7.0 or newer
  • Composer

The 1.x version of this module is available on the 1.x branch.Use this version if you still use TemplateEngineFactory 1.x.

Installation

Execute the following command in the root directory of your ProcessWire installation:

composer require dreerr/template-engine-pug:^2.0

This will install the TemplateEnginePug and TemplateEngineFactory modules in one step. Afterwards, don't forgetto enable Pug as engine in the TemplateEngineFactory module's configuration.

Configuration

The module offers the following configuration:

  • Template files suffix The suffix of the Pug template files, defaults to pug.
  • Provide ProcessWire API variables in templates API variables ($pages, $input, $config...)are accessible in Pug.
  • Output indented HTML If checked, the output is rendered as indented HTML.
  • Debug Output When an error occurs at render time, you will get a complete stack trace including line and offset in the original pug source file.
  • Enable Profiler When set to true, it will output on render a timeline you can inspect in your browser to see wich token/node take longer to lex/parse/compile/render.

Comments

No comments yet. Be the first to post!

Post a Comment

Your e-mail is kept confidential and not included with your comment. Website is optional.