- Getting Started
- Working with Templates
- Using Data
- Template Languages
- Release History
Glossary and Buzzwords #
Bask in the warm glow of this “Nobody ever got fired for buying IBM”-style feel-good industry jargon.
Our industry can be particularly bad about inventing words for things that already exist. Hopefully this page will help you navigate the labyrinth.
Work in progress: Edit this page on GitHub (in latest version)
Static Sites #
Progressive Enhancement #
Make components and markup data-driven so that you don’t have a bunch of one-off copy-pasted HTML instances littered throughout your project.
Serverless Friendly #
Lean Web #
To be honest it’s kind of a stretch to relate Lean methodology to this project but the term just kinda feels right.
Zero Config #
Zero config means that Eleventy can run without any command line parameters or configuration files.
We’ve taken care to setup Eleventy so that that running the stock
eleventy command uses sensible defaults. Lower the barrier to entry for that first project build to get up and running faster.
Convention over Configuration Routing #
Can you believe that some frameworks require a centralized piece of configuration for routing?
eleventy routes map the file system, unless you override with a
They’re not Server Side Rendered, they’re Pre-rendered #
Many frameworks switched to Server Side Rendering, which meant running an application server with middleware that would render the markup on demand for each request. While this is valuable, static sites are different. The templates are all generated (some call this pre-rendering) at build time for maximum performance. This way the web server only needs to fetch the static file and send it back to the user.
Apps not App Servers #
Application servers can be slow. Instead of PHP, Java, or even Node.js dynamically generating page responses on the fly when the request comes in, have your pre-rendered templates ready to go for delivery! Maximum performance.