|-_site                    ### files for deployment
|-src/
  |-_includes/             ### template files
  |-concepts/              ### posts relating to cooking concepts
    |-kitchen-glossary/    ### sub-posts for definitions
  |-drafts                 ### in eleventyignore
  |-icons/
  |-images/
  |-sass/
    |-defaults/            ### resets
  |-scripts/
  |-styles/                ### compiled css that gets copied to _site
|-.eleventy.js
|-.gitignore
|-gulpfile.js              ### primarily to process scss
|-LICENSE                  ### all files MIT (recipes cannot be copyrighted/licensed)
|-package-lock.json
|-package.json
|-README.md

• addPassthruCopy: icons, images, styles, js
• setDataDeepMerge(true) 11ty's docs ↗️
• using markdown-it, markdown-it-footnote, markdown-it-attrs
• customized collection that front-loads pinned material in the concepts section.

After cloning repo, run npm install and wait for all node modules to be installed.

npm run test #hello world equivalent
npm run develop #provides a server and live-rebuild environment on localhost:8080
npm run debug #runs DEBUG; uses globally installed debug package that spits out diagnostic info on the build process and any errors encountered
npm run newRecipe #creates new.md in drafts
npm run newConcept #creates new.md in drafts
npm run newDefinition # creates new.md in drafts.kitchen-glossary

Defaults found in their respective data file are shown in place. These terms do not have to be included in the front matter since 11ty's templating engine does this automatically. Types in comment as needed. I also have 11ty's setDataDeepMerge(true) so that nested collections inherit key-value pairs instead of overwriting them.

---
title: string
description: string
 date: leave blank or provide yyyy-mm-dd to override default date sort
layout: post.liquid
tags: ['posts', 'concepts']
sourceTitle: optional string
sourceURL: optional URL
sourceLicense:
  license: optional string
  URL: optional URL
---

---
title: string
description: string
date: Last Modified
layout: post.liquid
tags: ['posts', 'recipes']
sourceTitle: optional string
sourceURL: optional URL
sourceLicense:
  license: optional string
  URL: optional URL
---

---
title: string
description: string
date: Last Modified
layout: post.liquid
permalink: false
tags: ['posts', 'recipes', 'definitions']
sourceTitle: optional string
sourceURL: optional URL
sourceLicense:
  license: optional string
  URL: optional URL
---

This site nests illustrations inside the list items they support. This allows me to style the image without having to inline HTML in the markdown document. Images should appear before any words on the list item. This approach is not perfect because it does not take into account multiple pictures in close proximation of each other. Should it become a problem, it will be changed.

This site will eventually use the h-recipe microformat. Doing so provides structure that allows search engines and extraction utilities to determine the type of information that on each recipe page. I'm still working out the specifics of my approach but it will most likely use a combination of markdown-it-attr and another parser to apply the classes that make up the h-recipe microformat to the appropriate elements on the page.

• tags ftw
• Make nicer recipe.concept/definition generators
• Search/indexing
• How to journal in a recipe? Fermenation and bread experiments.
• Optionally link to cited source instead of always (forced to use anchor placeholder)
• Microformats
  • h-recipe microformat.
  • markdown-it-attrs documentation
• Nutrition API tie-in