1- <!doctype html>
1+ <!DOCTYPE html>
22< html lang ="en ">
33
44< head >
@@ -76,55 +76,11 @@ <h2>What is a branch in Git</h2>
7676
7777 </ main >
7878
79- < head >
80- < meta charset ="UTF-8 " />
81- < meta name ="viewport " content ="width=device-width, initial-scale=1.0 " />
82- < title > Wireframe</ title >
83- < link rel ="stylesheet " href ="style.css " />
84- </ head >
85-
86- < body >
87- < header >
88- < h1 > Wireframe Coursework</ h1 >
89- </ header >
90- < main >
91- < article >
92- < img src ="placeholder.svg " alt ="placeholder image " />
93- < h2 > Purpose of ReadME</ h2 >
94- < p >
95- Read me provides a quick overview of what the project sets to achieve,
96- the likely uses and the guidelines of how others can contribute.
97- </ p >
98- < a href =""> Read more</ a >
99- </ article >
100-
101- < article >
102- < img src ="placeholder2.png " alt ="Wireframe image " />
103- < h2 > Purpose of Wireframe</ h2 >
104- < p >
105- Wireframe serves as a foundational blueprint or mental image of a
106- product, it has numerous functions and most importantly wireframe is
107- often used in the early stages of web or app development to prevent
108- future, costly redesigns.
109- </ p >
110- < a href =""> Read more</ a >
111- </ article >
112- < article >
113- < img src ="Branch.png " alt ="Branch image " />
114- < h2 > What is a branch in Git</ h2 >
115- < p >
116- A branch represents an independent line of development in a Git
117- repository, allowing multiple developers to work on different features
118- or bug fixes simultaneously without affecting the main codebase until
119- changes are ready to be merged.
120- </ p >
121- < a href =""> Read more</ a >
122- </ article >
123- </ main >
124-
125- < footer >
126- < p > By Toluwalase Tiamiyu.</ p >
127- </ footer >
128- </ body >
79+ < footer >
80+ < p >
81+ By Toluwalase Tiamiyu.
82+ </ p >
83+ </ footer >
84+ </ body >
12985
13086</ html >
0 commit comments