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 > Welcome to Intro to Programming</ h1 >
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+ </ head >
10+
11+ < body >
12+ < header >
13+ < h1 > Welcome to Intro to Programming</ h1 >
14+ < p >
15+ Here we will learn about some introductory web development
16+ concepts.
17+ </ p >
18+ </ header >
19+ < main >
20+ < article >
21+ < img src ="https://cdn.bulldogjob.com/system/photos/files/000/003/440/original/readme.webp "
22+ alt ="example readme file " />
23+ < h2 > The purpose of a README file</ h2 >
1224 < p >
13- Here we will learn about some introductory web development
14- concepts.
25+ A README file is a text file often included with a software
26+ program or code package which provides the reader with
27+ information they may need to use the software, such as
28+ installation instructions.
1529 </ p >
16- </ header >
17- < main >
18- < article >
19- < img
20- src ="https://cdn.bulldogjob.com/system/photos/files/000/003/440/original/readme.webp "
21- alt ="example readme file " />
22- < h2 > The purpose of a README file</ h2 >
23- < p >
24- A README file is a text file often included with a software
25- program or code package which provides the reader with
26- information they may need to use the software, such as
27- installation instructions.
28- </ p >
29- < a
30- href ="https://bulldogjob.com/readme/how-to-write-a-good-readme-for-your-github-project "
31- > Write your own README file</ a
32- >
33- </ article >
34- < article >
35- < img
36- src ="https://cdn-images.visual-paradigm.com/handbooks/agile-handbook/wireframe/01-youtube-wireframe-example.png "
37- alt ="example of a wireframe " />
38- < h2 > The purpose of a wireframe</ h2 >
39- < p >
40- A wireframe is used to express the layout of a visual medium
41- such as a newspaper, or web page. It helps designers and
42- programmers to get a simple overview of a design.
43- </ p >
44- < a
45- href ="https://www.figma.com/resource-library/what-is-wireframing/ "
46- > Read more about wireframing</ a
47- >
48- </ article >
49- < article >
50- < img
51- src ="https://miro.medium.com/v2/resize:fit:1200/format:webp/1*e6EkEBIDZcOmlwPqCnsJKg.jpeg "
52- alt ="diagram of git branching " />
53- < h2 > What is a Git branch</ h2 >
54- < p >
55- A git branch is a copy of the code in a git repository.
56- Branches are created so that developers can work separately
57- on specific features. Once a feature is completed it is
58- merged into main. If the creation of a feature is not
59- successful, for example there are too many bugs, the branch
60- can be deleted without affecting the main branch.
61- </ p >
62- < a
63- href ="https://medium.com/@jacoblogan98/understanding-git-branching-5d01f3dda541 "
64- > Read more about Git</ a
65- >
66- </ article >
67- </ main >
68- < footer >
30+ < a href ="https://bulldogjob.com/readme/how-to-write-a-good-readme-for-your-github-project "> Write your own
31+ README file</ a >
32+ </ article >
33+ < article >
34+ < img src ="https://cdn-images.visual-paradigm.com/handbooks/agile-handbook/wireframe/01-youtube-wireframe-example.png "
35+ alt ="example of a wireframe " />
36+ < h2 > The purpose of a wireframe</ h2 >
6937 < p >
70- Completed by Gideon Defar for ITP at Code Your
71- Future.
38+ A wireframe is used to express the layout of a visual medium
39+ such as a newspaper, or web page. It helps designers and
40+ programmers to get a simple overview of a design.
7241 </ p >
73- </ footer >
74- </ body >
42+ < a href ="https://www.figma.com/resource-library/what-is-wireframing/ "> Read more about wireframing</ a >
43+ </ article >
44+ < article >
45+ < img src ="https://miro.medium.com/v2/resize:fit:1200/format:webp/1*e6EkEBIDZcOmlwPqCnsJKg.jpeg "
46+ alt ="diagram of git branching " />
47+ < h2 > What is a Git branch</ h2 >
48+ < p >
49+ A git branch is a copy of the code in a git repository.
50+ Branches are created so that developers can work separately
51+ on specific features. Once a feature is completed it is
52+ merged into main. If the creation of a feature is not
53+ successful, for example there are too many bugs, the branch
54+ can be deleted without affecting the main branch.
55+ </ p >
56+ < a href ="https://medium.com/@jacoblogan98/understanding-git-branching-5d01f3dda541 "> Read more about Git</ a >
57+ </ article >
58+ </ main >
59+ < footer >
60+ < p >
61+ Completed by Gideon Defar for Code Your
62+ Future.
63+ </ p >
64+ </ footer >
65+ </ body >
66+
7567</ html >
0 commit comments