22< html lang ="en ">
33
44< head >
5- < meta charset ="UTF-8 ">
6- < meta name ="viewport " content ="width=device-width, initial-scale=1.0 ">
7- < title >
8- About Wireframes, READMEs and Git Branches
9- </ title >
10- < link rel ="stylesheet " href ="style.css ">
5+ < meta charset ="UTF-8 " />
6+ < meta name ="viewport " content ="width=device-width, initial-scale=1.0 " />
7+ < title > Wireframe</ title >
8+ < link rel ="stylesheet " href ="style.css " />
119</ head >
1210
1311< body >
1412 < header >
1513 < h1 >
16- About Wireframes, READMEs and Git Branches
14+ < ul >
15+ < li >
16+ What is the purpose of a README file?
17+ </ li >
18+ < li >
19+ What is the purpose of a wireframe?
20+ </ li >
21+ < li >
22+ What is a branch in Git?
23+ </ li >
24+ </ ul >
25+ This is the webpage to provide detail explanation for the above questions
1726 </ h1 >
18- < p >
19- This page explores wireframes in web design, the significance of README
20- files in software projects and the role of branches in Git version
21- control.
22- </ p >
2327 </ header >
2428 < main >
2529 < article >
26- < img src ="placeholder .svg " alt ="">
27- < h2 > Wireframe </ h2 >
30+ < img src ="readme .svg " alt ="" / >
31+ < h2 > What is the purpose of a README file? </ h2 >
2832 < p >
29- Wireframe provides a foundational structural template for web pages.
30- It serves as a communication tool for stakeholders, web designers and
31- developers, providing a simple structural view of the rendered web
32- page.
33+ A README file is the foundational documentation for a software, dataset, or coding project. It serves as a
34+ project's "front door," designed to help users quickly understand what the project does, how to install and use
35+ it, and how to contribute
3336 </ p >
3437 < a
35- href ="https://www.wix .com/blog/what-are-wireframes?experiment_id=%5E%5E40312ac7-ca22-4ba2-bd8e-0b726ed32275%5E "> Read
38+ href ="https://docs.github .com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes "> Read
3639 more</ a >
3740 </ article >
41+
3842 < article >
39- < img src ="placeholder .svg " alt ="">
40- < h2 > README Files </ h2 >
43+ < img src ="wireframe .svg " alt ="" / >
44+ < h2 > What is the purpose of a wireframe? </ h2 >
4145 < p >
42- README files offer essential explanatory information about a codebase
43- within a repository, including usage instructions and details about
44- its features.
46+ Wireframes are the foundational blueprints of a website or app. Used early in the development process, they help
47+ teams visualize structure, map user flows, and establish content hierarchy before committing to costly colors,
48+ branding, or final UI design
4549 </ p >
46- < a href ="https://www.makeareadme .com/ "> Read more</ a >
50+ < a href ="https://www.productplan .com/glossary/wireframe / "> Read more</ a >
4751 </ article >
52+
4853 < article >
49- < img src ="placeholder .svg " alt ="">
50- < h2 > Git branches </ h2 >
54+ < img src ="branch .svg " alt ="" / >
55+ < h2 > What is a branch in Git? </ h2 >
5156 < p >
52- Git branches are a fundamental feature that enables users to develop
53- features and make commits independently of the main branch. This
54- facilitates parallel development by multiple teams without causing
55- conflicts directly.
57+ A branch in Git is simply a lightweight movable pointer to one of these commits. The default branch name in Git
58+ is master .
5659 </ p >
57- < a href ="https://git-scm. com/book/en/v2/Git-Branching-Branches-in-a-Nutshell "> Read more</ a >
60+ < a href ="https://www.w3schools. com/GIT/git_branch.asp?remote=github "> Read more</ a >
5861 </ article >
5962 </ main >
6063 < footer >
61- This all about wireframe. All Rights Reserved.
64+ < p >
65+ By Gideon Defar
66+ </ p >
6267 </ footer >
6368</ body >
69+
6470</ html >
0 commit comments