From 322f3e7e61383891426091a97ce051c9aa2582c4 Mon Sep 17 00:00:00 2001 From: Keith Curry <104702773+Keiferton@users.noreply.github.com> Date: Thu, 26 Dec 2024 19:26:25 -0800 Subject: [PATCH 1/5] Update project-recipes.md add instructions for back link from recipes to homepage (index.html) --- foundations/html_css/html-foundations/project-recipes.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/foundations/html_css/html-foundations/project-recipes.md b/foundations/html_css/html-foundations/project-recipes.md index a9237d1883..437220fbb6 100644 --- a/foundations/html_css/html-foundations/project-recipes.md +++ b/foundations/html_css/html-foundations/project-recipes.md @@ -63,6 +63,11 @@ Okay, that's enough Git for the moment -- time to actually build stuff! 1. Create a new HTML file within the `recipes` directory and name it after the recipe it will contain. For example `lasagna.html`. You can use the name of your favorite dish or, if you need some inspiration, you can find a recipe to use at [Allrecipes](https://www.allrecipes.com/). Be sure to include the usual boilerplate HTML. This boilerplate code should be in every `.html` file you create. 1. For now, just include an `h1` heading with the recipe's name as its content. 1. Back in the `index.html` file, add a link to the recipe page you just created. Example: Under the `

Odin Recipes

` heading, write out the link like so: `Recipe Title`. The text of the link should again be the recipe name. +1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., 'lasagna.html'). Here's and example: + '''html + Home + ''' + This allows users to quickly return to the home page after viewing the recipe. #### Iteration 3: recipe page content From d7bcb5eddd713356ef9f3f633a4ee7b2e1b5c1ff Mon Sep 17 00:00:00 2001 From: Keith Curry <104702773+Keiferton@users.noreply.github.com> Date: Sat, 28 Dec 2024 15:42:52 -0800 Subject: [PATCH 2/5] Update project-recipes.md fix typo and use correct markdown syntax for backlink html example --- foundations/html_css/html-foundations/project-recipes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/foundations/html_css/html-foundations/project-recipes.md b/foundations/html_css/html-foundations/project-recipes.md index 437220fbb6..653985dc80 100644 --- a/foundations/html_css/html-foundations/project-recipes.md +++ b/foundations/html_css/html-foundations/project-recipes.md @@ -63,10 +63,10 @@ Okay, that's enough Git for the moment -- time to actually build stuff! 1. Create a new HTML file within the `recipes` directory and name it after the recipe it will contain. For example `lasagna.html`. You can use the name of your favorite dish or, if you need some inspiration, you can find a recipe to use at [Allrecipes](https://www.allrecipes.com/). Be sure to include the usual boilerplate HTML. This boilerplate code should be in every `.html` file you create. 1. For now, just include an `h1` heading with the recipe's name as its content. 1. Back in the `index.html` file, add a link to the recipe page you just created. Example: Under the `

Odin Recipes

` heading, write out the link like so: `Recipe Title`. The text of the link should again be the recipe name. -1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., 'lasagna.html'). Here's and example: - '''html +1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., 'lasagna.html'). Here's an example: + ```html Home - ''' + ``` This allows users to quickly return to the home page after viewing the recipe. #### Iteration 3: recipe page content From 674a295363730678f65172cb76a9bcafb9b3ec2b Mon Sep 17 00:00:00 2001 From: Keith Curry <104702773+Keiferton@users.noreply.github.com> Date: Mon, 30 Dec 2024 22:32:30 -0800 Subject: [PATCH 3/5] fix lint errors - add blank line before and after fenced html - ignore capitalization, html is not used as a noun here --- .../html_css/html-foundations/project-recipes.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/foundations/html_css/html-foundations/project-recipes.md b/foundations/html_css/html-foundations/project-recipes.md index 653985dc80..b72e9976b0 100644 --- a/foundations/html_css/html-foundations/project-recipes.md +++ b/foundations/html_css/html-foundations/project-recipes.md @@ -64,10 +64,12 @@ Okay, that's enough Git for the moment -- time to actually build stuff! 1. For now, just include an `h1` heading with the recipe's name as its content. 1. Back in the `index.html` file, add a link to the recipe page you just created. Example: Under the `

Odin Recipes

` heading, write out the link like so: `Recipe Title`. The text of the link should again be the recipe name. 1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., 'lasagna.html'). Here's an example: - ```html - Home - ``` - This allows users to quickly return to the home page after viewing the recipe. + + ```html + Home + ``` + + This allows users to quickly return to the home page after viewing the recipe. #### Iteration 3: recipe page content From b0b4d3bab693fe456e13f7269ce4a4d2e3b37384 Mon Sep 17 00:00:00 2001 From: Keith Curry <104702773+Keiferton@users.noreply.github.com> Date: Mon, 30 Dec 2024 22:36:54 -0800 Subject: [PATCH 4/5] Update project-recipes.md --- foundations/html_css/html-foundations/project-recipes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/foundations/html_css/html-foundations/project-recipes.md b/foundations/html_css/html-foundations/project-recipes.md index b72e9976b0..1800eac9ca 100644 --- a/foundations/html_css/html-foundations/project-recipes.md +++ b/foundations/html_css/html-foundations/project-recipes.md @@ -63,7 +63,7 @@ Okay, that's enough Git for the moment -- time to actually build stuff! 1. Create a new HTML file within the `recipes` directory and name it after the recipe it will contain. For example `lasagna.html`. You can use the name of your favorite dish or, if you need some inspiration, you can find a recipe to use at [Allrecipes](https://www.allrecipes.com/). Be sure to include the usual boilerplate HTML. This boilerplate code should be in every `.html` file you create. 1. For now, just include an `h1` heading with the recipe's name as its content. 1. Back in the `index.html` file, add a link to the recipe page you just created. Example: Under the `

Odin Recipes

` heading, write out the link like so: `Recipe Title`. The text of the link should again be the recipe name. -1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., 'lasagna.html'). Here's an example: +1. **Add a link back to the index page** on your recipe page for easier navigation. You can place this link at the top or bottom of your recipe page (e.g., `lasagna.html`). Here's an example: ```html Home From 897698c8452cffdb994535b42c6bb61eeb0a0912 Mon Sep 17 00:00:00 2001 From: Keith Curry <104702773+Keiferton@users.noreply.github.com> Date: Wed, 1 Jan 2025 19:03:39 -0800 Subject: [PATCH 5/5] remove indent on line 71 causing linter error the linter showed an error on line 71, I believe it to be from a line break on an indented line, removed indent --- foundations/html_css/html-foundations/project-recipes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/foundations/html_css/html-foundations/project-recipes.md b/foundations/html_css/html-foundations/project-recipes.md index 1800eac9ca..5982c37063 100644 --- a/foundations/html_css/html-foundations/project-recipes.md +++ b/foundations/html_css/html-foundations/project-recipes.md @@ -68,7 +68,7 @@ Okay, that's enough Git for the moment -- time to actually build stuff! ```html Home ``` - + This allows users to quickly return to the home page after viewing the recipe. #### Iteration 3: recipe page content