Eleventy Supplied Data #

Here are a few data values we supply to your page that you can use in your templates:

• pkg: The local project’s package.json values.
• pagination, when enabled using pagination in front matter. Read more about Pagination.
• collections: Lists of all of your content, grouped by tags. Read more about Collections
• page: Has information about the current page. See code block below for page contents. For example, page.url is useful for finding the current page in a collection. Read more about Collections (look at Example: Navigation Links with an active class added for on the current page).
• eleventy: New in v1.0.0 contains Eleventy-specific data from environment variables and the Serverless plugin (if used).

page Variable: #

let page = {

  // URL can be used in <a href> to link to other templates
  // Note: This value will be `false` if `permalink` is set to `false`.
  url: "/current/page/myFile/",

  // For permalinks: inputPath filename minus template file extension
  fileSlug: "myFile",

  // For permalinks: inputPath minus template file extension
  filePathStem: "/current/page/myFile",

  // JS Date Object for current page (used to sort collections)
  date: new Date(),

  // The path to the original source file for the template
  // Note: this will include your input directory path!
  inputPath: "./current/page/myFile.md",

  // Depends on your output directory (the default is _site)
  // You probably won’t use this: `url` is better.
  // Note: This value will be `false` if `permalink` is set to `false`.
  outputPath: "./_site/current/page/myFile/index.html",

  // Added in 1.0
  // Useful with `page.filePathStem` when using custom file extensions.
  outputFileExtension: "html"
};

date #

The date associated with the page. Defaults to the content’s file created date but can be overridden. Read more at Content Dates.

fileSlug #

The fileSlug variable is mapped from inputPath and is useful for creating your own clean permalinks.

fileSlug returns information on the parent directory if the file is an index template:

filePathStem #

The filePathStem variable is mapped from inputPath and is useful if you’ve inherited a project that doesn’t use clean permalinks.

If you absolutely need a file extension on your output, you might use it like this:

---
permalink: "{{ page.filePathStem }}.html"
---

Example Output below is using the above permalink value.

eleventy Variable New in v1.0.0 #

let eleventy = {

  // Eleventy version
  version: "1.0.1", // New in Eleventy v1.0.1

  // For use with `<meta name="generator">`
  generator: "Eleventy v1.0.1", // New in Eleventy v1.0.1

  // Read more about their `process.env` counterparts below
  env: {
    // Absolute path to the directory in which
    // you’ve run the Eleventy command.
    root: "/Users/zachleat/myProject/",

    // Absolute path to the current config file
    config: "/Users/zachleat/myProject/.eleventy.js",

    // The method, either `cli` or `script`
    source: "cli",
  },

  serverless: {
    // An object containing the values from any Dynamic URL
    //   slugs from Serverless paths
    // e.g. A slug for /path/:id/ and a URL for /path/1/
    //   would give { id: 1 }
    path: {}

    // The `event.queryStringParameters` received from the
    // serverless function. Note these are not available in
    // Netlify On-demand Builders
    // e.g. ?id=1 would be { id: 1 }
    query: {},
  }

};

Learn more about:

• Eleventy-supplied Environment Variables on process.env
• Serverless
  • Dynamic Slugs and Serverless Global Data.
  • event.queryStringParameters, which are very similar to URL.searchParams. It’s an object representing the name/value pairs for things after the ? in a URL.

Eleventy Leaderboards:

• Upcoming versions of the Eleventy Leaderboards will require that <meta name="generator" content="{{ eleventy.generator }}"> New in v1.0.1 exist on the page’s markup to be valid for placement and ranking.

Environment Variables on process.env #

• Read more about Eleventy-supplied environment variables.

Other pages in Using Data:

• Configure your Templates
• Eleventy Supplied Data
• Data Cascade
  • Front Matter Data
    • Customize Front Matter Parsing
  • Template & Directory Data Files
  • Global Data Files
    • Data Preprocessing
  • Data Deep Merge
  • Config Global Data
  • Computed Data
• Environment Variables
• JavaScript Data Files
• Custom Data File Formats