Book Image

Eleventy By Example

By : Bryan Robinson
Book Image

Eleventy By Example

By: Bryan Robinson

Overview of this book

11ty is the dark horse of the Jamstack world, offering unparalleled flexibility and performance that gives it an edge against other static site generators such as Jekyll and Hugo. With it, developers can leverage the complete Node ecosystem and create blazing-fast, static-first websites that can be deployed from a content delivery network or a simple server. This book will teach you how to set up, customize, and make the most of 11ty in no time. Eleventy by Example helps you uncover everything you need to create your first 11ty website before diving into making more complex sites and extending 11ty’s base functionality with custom short codes, plugins, and content types. Over the course of 5 interactive projects, you’ll learn how to build basic websites, blogs, media sites, and static sites that will respond to user input without the need for a server. With these, you’ll learn basic 11ty skills such as templates, collections, and data use, along with advanced skills such as plugin creation, image manipulation, working with a headless CMS, and the use of the powerful 11ty Serverless plugin. By the end of this book, you’ll be well-equipped to leverage the capabilities of 11ty by implementing best practices and reusable techniques that can be applied across multiple projects, reducing the website launch time.
Table of Contents (13 chapters)

Technical requirements

This project has a little less setup than the full website projects we’ve built in this book. We want to keep the plugin directories as clean as possible. As usual, there’s a project folder in the book’s GitHub repository at https://github.com/PacktPublishing/Eleventy-by-Example that has a solid starting point for each plugin. You’ll also want access to the previous projects’ code, as we’ll be using code we’ve already written to create these plugins.

Each plugin we create in this chapter starts from a basic file structure. While we covered best practice project structure in Chapter 1, those best practices were for websites. We want each of these plugins to have as little configuration as possible, so we use the default 11ty structure. Because of this, we don’t have an src directory and don’t rearrange the layouts and includes separately. The basic project structure for each is a package.json file...