11<!DOCTYPE html>
22< html lang ="en ">
3- < head >
4- < meta charset ="UTF-8 " />
5- < meta name ="viewport " content ="width=device-width, initial-scale=1.0 " />
6- < title > Wireframe</ title >
7- < link rel ="stylesheet " href ="style.css " />
8- </ head >
9- < body >
10- < header >
11- < h1 > Wireframe</ h1 >
12- < p >
13- This is the default, provided code and no changes have been made yet.
14- </ p >
15- </ header >
16- < main >
17- < article >
18- < img src ="placeholder.svg " alt ="" />
19- < h2 > Title</ h2 >
20- < p >
21- Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
22- voluptates. Quisquam, voluptates.
3+
4+ < head >
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 ">
9+ < link rel ="preconnect " href ="https://fonts.googleapis.com ">
10+ < link rel ="preconnect " href ="https://fonts.gstatic.com " crossorigin >
11+
12+ < link href ="https://fonts.googleapis.com/css2?family=Kalam:wght@400;700&family=Inter:wght@400;600&display=swap "
13+ rel ="stylesheet ">
14+ < meta name ="description " content =" Learn about README files, wireframes, and Git branches. ">
15+
16+ </ head >
17+
18+ < body >
19+ < header class ="page-hero ">
20+ < h1 class ="page-hero "> Wireframe</ h1 >
21+ < p class ="page-subtitle ">
22+ Learn about README files, wireframes, and Git branches.
23+ </ p >
24+ </ header >
25+ < main class ="container ">
26+ <!-- Featured card (full width) -->
27+ < article class ="card card--featured ">
28+ < div class ="card__media ">
29+ < img src ="https://images.unsplash.com/photo-1516321318423-f06f85e504b3 "
30+ alt ="Person reading project documentation ">
31+ </ div >
32+ < div class ="card__body ">
33+ < h2 class ="card__title "> What is the purpose of a README file?</ h2 >
34+ < p class ="card__summary ">
35+ A README introduces a project: what it is, why it exists, and how to use, install, run, and contribute to it.
36+ It orients new users and contributors, sets expectations (requirements, license, roadmap), and centralizes
37+ quick-start commands and links. In short, it’s the project’s front door and owner’s manual.
2338 </ p >
24- < a href =""> Read more</ a >
39+ < a class ="btn " href ="#readme-details "> Read More</ a >
40+ </ div >
41+ </ article >
42+
43+
44+ <!-- Two-column row -->
45+ < div class ="grid ">
46+ < article class ="card ">
47+ < div class ="card__media ">
48+ < img src ="https://images.unsplash.com/photo-1516321318423-f06f85e504b3 "
49+ alt ="Person reading project documentation ">
50+ </ div >
51+ < div class ="card__body ">
52+ < h2 class ="card__title "> What is the purpose of a wireframe?</ h2 >
53+ < p class ="card__summary ">
54+ A wireframe is a low‑fidelity layout of a page. It maps structure, hierarchy, and placement of elements
55+ (headers, media, text, buttons) without visual polish. Teams use wireframes to align on content priority,
56+ user flow, and functionality early—reducing rework before design and code.
57+ </ p >
58+ < a class ="btn " href ="#wireframe-details "> Read More</ a >
59+ </ div >
2560 </ article >
26- </ main >
27- < footer >
28- < p >
29- This is the default, provided code and no changes have been made yet.
30- </ p >
31- </ footer >
32- </ body >
33- </ html >
61+
62+ < article class ="card ">
63+ < div class ="card__media ">
64+ < img src ="https://images.unsplash.com/photo-1555949963-aa79dcee981c "
65+ alt ="Developer working with Git and code ">
66+ </ div >
67+ < div class ="card__body ">
68+ < h2 class ="card__title "> What is a branch in Git?</ h2 >
69+ < p class ="card__summary ">
70+ A Git branch is an independent line of development. It lets you make changes, experiment, and review work
71+ without affecting the main history. When ready, merge the branch back (often via pull request) to integrate
72+ tested, reviewed changes into the primary codebase.
73+ </ p >
74+ < a class ="btn " href ="#git-branch-details "> Read More</ a >
75+ </ div >
76+ </ article >
77+ </ div >
78+
79+ <!-- “read more” anchors -->
80+ < section class ="details " id ="readme-details " aria-label ="README details ">
81+ < h3 > README essentials</ h3 >
82+ < ul >
83+ < li > Project overview and goals</ li >
84+ < li > Installation and quick start</ li >
85+ < li > Usage examples and configuration</ li >
86+ < li > Contributing guidelines and license</ li >
87+ < li > Links to docs, issues, and support</ li >
88+ </ ul >
89+ </ section >
90+
91+ < section class ="details " id ="wireframe-details " aria-label ="Wireframe details ">
92+ < h3 > Why wireframe first</ h3 >
93+ < ul >
94+ < li > Clarifies content priority and layout</ li >
95+ < li > Enables fast feedback before visuals</ li >
96+ < li > De-risks scope and uncovers edge cases</ li >
97+ < li > Acts as a blueprint for designers/devs</ li >
98+ </ ul >
99+ </ section >
100+
101+ < section class ="details " id ="git-branch-details " aria-label ="Git branch details ">
102+ < h3 > Branch workflow highlights</ h3 >
103+ < ul >
104+ < li > Create: git checkout -b feature/name</ li >
105+ < li > Commit work locally and push the branch</ li >
106+ < li > Open a pull request for review and CI</ li >
107+ < li > Merge, then delete the branch when done</ li >
108+ </ ul >
109+ </ section >
110+
111+ </ main >
112+ < footer class ="site-footer ">
113+ < p >
114+ Liyema Mfengwana sprint 2 wireframe backlog.
115+ </ p >
116+ </ footer >
117+ </ body >
118+
119+ </ html >
0 commit comments