- Getting Started
- Working with Templates
- Using Data
- Template Languages
- Release History
Having trouble? Want to see what Eleventy is doing behind the scenes? Use
DEBUG mode. We’re taking advantage of the excellent
debug package for this. Enable with the
DEBUG env variable, either specific to eleventy (
DEBUG=Eleventy*) or globally (
It’s different if you’re on Windows.
This will tell you exactly what directories Eleventy is using for data, includes, input, and output. It’ll tell you what search globs it uses to find your templates and what templates it finds. If you’re having trouble, enable this.
Works great with
--dryrun if you want to run Eleventy but not actually write any files.
Read more at the
debug package documentation.