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 > Web Development Concepts</ h1 >
12- < p > Understanding README files, Wireframes and Git Branches</ p >
13- </ header >
143
15- < main >
16- < article >
17- < img src ="images/readme.png " alt ="README documentation example " />
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+ </ head >
1810
11+ < body >
12+ < header >
13+ < h1 > Web Development Concepts</ h1 >
14+ < p > Understanding README files, Wireframes and Git Branches</ p >
15+ </ header >
1916
20- < h2 > What is a README File?</ h2 >
17+ < main >
18+ < article >
19+ < img src ="images/readme.png " alt ="README documentation example " />
2120
22- < p >
23- A README file explains a project. It usually contains information
24- about the purpose of the project, installation instructions,
25- usage examples and important notes for developers.
26- </ p >
2721
28- < a href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes ">
29- Read More
30- </ a >
22+ < h2 > What is a README File?</ h2 >
3123
32- </ article >
24+ < p >
25+ A README file explains a project. It usually contains information
26+ about the purpose of the project, installation instructions,
27+ usage examples and important notes for developers.
28+ </ p >
3329
34- < article >
35- < img src ="images/wireframe-topic.png " alt ="Website wireframe layout sketch " />
30+ < a
31+ href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes ">
32+ Read More
33+ </ a >
3634
37- < h2 > What is a Wireframe? </ h2 >
35+ </ article >
3836
39- < p >
40- A wireframe is a visual plan of a webpage. It helps designers
41- and developers organise content and layout before building
42- the final website.
43- </ p >
37+ < article >
38+ < img src ="images/wireframe-topic.png " alt ="Website wireframe layout sketch " />
4439
45- < a href ="https://www.interaction-design.org/literature/topics/wireframing ">
46- Read More
47- </ a >
40+ < h2 > What is a Wireframe?</ h2 >
4841
49- </ article >
42+ < p >
43+ A wireframe is a visual plan of a webpage. It helps designers
44+ and developers organise content and layout before building
45+ the final website.
46+ </ p >
5047
51- < article >
52- < img src ="images/branch.png " alt ="Git branching workflow diagram " />
48+ < a href ="https://www.interaction-design.org/literature/topics/wireframing ">
49+ Read More
50+ </ a >
5351
54- < h2 > What is a Git Branch? </ h2 >
52+ </ article >
5553
56- < p >
57- A Git branch is an independent line of development.
58- It allows developers to work on new features without
59- affecting the main version of a project.
60- </ p >
54+ < article >
55+ < img src ="images/branch.png " alt ="Git branching workflow diagram " />
6156
62- < a href ="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell ">
63- Read More
64- </ a >
57+ < h2 > What is a Git Branch?</ h2 >
6558
66- </ article >
67- </ main >
59+ < p >
60+ A Git branch is an independent line of development.
61+ It allows developers to work on new features without
62+ affecting the main version of a project.
63+ </ p >
6864
69- < footer >
70- < p > Contact information and site details </ p >
71- </ footer >
65+ < a href =" https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell " >
66+ Read More
67+ </ a >
7268
73- </ body >
74- </ html >
69+ </ article >
70+ </ main >
71+
72+ < footer >
73+ < p > Contact information and site details</ p >
74+ </ footer >
75+
76+ </ body >
77+
78+ </ html >
0 commit comments