From 997f522926405e86ec50311ffdd82e1a6087aaa0 Mon Sep 17 00:00:00 2001 From: Salman Hossain Saif Date: Thu, 23 Mar 2023 16:47:12 +0600 Subject: [PATCH] Tag needs to be `posts` not `post` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f1e71e8..f906fef 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ Deploy this Eleventy site in just a few clicks on these services: ### Implementation Notes - `content/about/index.md` is an example of a content page. -- `content/blog/` has the blog posts but really they can live in any directory. They need only the `post` tag to be included in the blog posts [collection](https://www.11ty.dev/docs/collections/). +- `content/blog/` has the blog posts but really they can live in any directory. They need only the `posts` tag to be included in the blog posts [collection](https://www.11ty.dev/docs/collections/). - Use the `eleventyNavigation` key (via the [Eleventy Navigation plugin](https://www.11ty.dev/docs/plugins/navigation/)) in your front matter to add a template to the top level site navigation. This is in use on `content/index.njk` and `content/about/index.md`. - Content can be in _any template format_ (blog posts needn’t exclusively be markdown, for example). Configure your project’s supported templates in `eleventy.config.js` -> `templateFormats`. - The `public` folder in your input directory will be copied to the output folder (via `addPassthroughCopy` in the `eleventy.config.js` file). This means `./public/css/*` will live at `./_site/css/*` after your build completes.