From 42c9aaa0af9641e57ca0200f55d4e19beeb8c63d Mon Sep 17 00:00:00 2001 From: Corey Oordt Date: Sun, 5 May 2024 09:04:23 -0500 Subject: [PATCH] Fixed readme images !minor --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2aaf4df..2fec5b9 100644 --- a/README.md +++ b/README.md @@ -30,15 +30,15 @@ Cookie composer builds on the [cookie cutter](https://github.com/cookiecutter/co Cookie Cutter treats templates like sandwiches. There are templates for hamburgers, clubs, and any other kind of sandwich you can dream up. You might have options and defaults on a template, like `Hold the mustard?[False]:` or `Mustard type [dijon]:`, but those are decided by the template author. -Templates are treated like finished sandwiches +Templates are treated like finished sandwiches If you look closely at the sandwiches (templates), there is usually many things in common. What if we treated the templates as compositions of other templates: -Sandwiches as a composition of layers +Sandwiches as a composition of layers You now can manage several smaller and specialized templates that provide functionality. Each template's options will be specific to what that template needs. -Templates broken out as layers on a sandwich +Templates broken out as layers on a sandwich Cookie Composer uses a composition file to describe the layers required, and even override a template's default answers.