11<!doctype html>
22< html lang ="en ">
3-
43< head >
54 < meta charset ="UTF-8 " />
65 < meta name ="viewport " content ="width=device-width, initial-scale=1.0 " />
7- < title > Wireframe</ title >
6+ < title > Wireframe | Process </ title >
87 < link rel ="stylesheet " href ="style.css " />
98 < link rel ="preconnect " href ="https://fonts.googleapis.com " />
109 < link rel ="preconnect " href ="https://fonts.gstatic.com " crossorigin />
11- < link href ="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,100..900;1,100..900&display=swap "
12- rel ="stylesheet " />
10+ < link href ="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,100..900;1,100..900&display=swap " rel ="stylesheet " />
1311</ head >
14-
1512< body >
1613 < header >
1714 < h1 > STARTING SIMPLE</ h1 >
1815 < h2 > Breaking down the development process</ h2 >
1916 </ header >
17+
2018 < main >
2119 < article >
22- < img src ="placeholder.svg " alt ="placeholder " />
20+ < img src ="placeholder.svg " alt ="A sample README file structure " />
2321 < div class ="content ">
2422 < h2 > README.md</ h2 >
2523 < p >
2624 The purpose of a README is to explain what the project is about. It
2725 provides a summary of the project, the technology stack used, and
2826 instructions for any required dependencies.
2927 </ p >
30- < a
31- href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes "> Read
32- more</ a >
28+ < a href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes "> Read more</ a >
3329 </ div >
3430 </ article >
31+
3532 < article >
36- < img src ="placeholder.svg " alt ="placeholder " />
33+ < img src ="placeholder.svg " alt ="A simple website wireframe " />
3734 < div class ="content ">
3835 < h2 > Wireframe</ h2 >
3936 < p >
4037 A wireframe is like a draft for your project. It shows where things
4138 will go and how they work before you add colors, images, or final
42- design details to guide the design process .
39+ design details.
4340 </ p >
44- < a href ="ttps ://www.productplan.com/glossary/wireframe/ "> Read more</ a >
41+ < a href ="https ://www.productplan.com/glossary/wireframe/ "> Read more</ a >
4542 </ div >
4643 </ article >
44+
4745 < article >
48- < img src ="placeholder.svg " alt ="placeholder " />
46+ < img src ="placeholder.svg " alt ="Diagram of a Git branch " />
4947 < div class ="content ">
5048 < h2 > A Branch in Git</ h2 >
5149 < p >
5250 A Git branch is a separate line of development within a repository.
53- It lets you work on new features or fixes independently without
54- affecting the main code until you are ready to merge.
51+ It lets you work on features independently without affecting the main code.
5552 </ p >
56- < a
57- href ="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches "> Read
58- more</ a >
53+ < a href ="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches "> Read more</ a >
5954 </ div >
6055 </ article >
6156 </ main >
57+
6258 < footer >
63- < p > Wireframe| Sprint 1| 2026</ p >
59+ < p > Wireframe | Sprint 1 | 2026</ p >
6460 </ footer >
6561</ body >
66-
6762</ html >
0 commit comments