@@ -22,84 +22,82 @@ <h1>Understanding README Files, Wireframes and Git Branches</h1>
2222 </ header >
2323
2424 < main >
25+ < article >
26+ < img src ="readme.png " alt ="README file example ">
2527
26- < article >
27- < h2 > What is a README File?</ h2 >
28-
29- < img src ="readme.png " alt ="README file example ">
30-
31- < p >
32- A README file is usually the first document people see when they visit a
33- project. It provides an overview of the project, explains its purpose,
34- gives installation instructions and helps users understand how to use
35- the software.
36- </ p >
37-
38- < p >
39- A well-written README makes it easier for developers and contributors
40- to understand and work with a project.
41- </ p >
42-
43- < a
44- href ="https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/ "
45- target ="_blank "
46- rel ="noopener noreferrer "
47- >
48- Learn more about README files
49- </ a >
50- </ article >
51-
52- < article >
53- < h2 > What is a Wireframe?</ h2 >
54-
55- < img src ="wireframe.png " alt ="Website wireframe example ">
56-
57- < p >
58- A wireframe is a simple visual representation of a webpage or
59- application. It focuses on structure and layout rather than colours,
60- images or final design elements.
61- </ p >
62-
63- < p >
64- Fun fact: designers use wireframes to plan where content, navigation and key
65- features will appear before development begins.
66- </ p >
67-
68- < a
69- href ="https://balsamiq.com/blog/what-are-wireframes/ "
70- target ="_blank "
71- rel ="noopener noreferrer "
72- >
73- Learn more about wireframes
74- </ a >
75- </ article >
76-
77- < article >
78- < h2 > What is a Git Branch?</ h2 >
79-
80- < img src ="git-branch.png " alt ="Git branch diagram ">
81-
82- < p >
83- A Git branch is an independent line of development within a Git
84- repository. It allows developers to work on new features, bug fixes or
85- experiments without affecting the main version of the project.
86- </ p >
87-
88- < p >
89- Once the work is complete and tested, the branch can be merged back into
90- the main codebase.
91- </ p >
92-
93- < a
94- href ="https://www.atlassian.com/git/tutorials/using-branches "
95- target ="_blank "
96- rel ="noopener noreferrer "
97- >
98- Learn more about Git branches
99- </ a >
100- </ article >
101-
102- </ main >
28+ < h2 > What is a README File?</ h2 >
29+
30+ < p >
31+ A README file is usually the first document people see when they visit a
32+ project. It provides an overview of the project, explains its purpose,
33+ gives installation instructions and helps users understand how to use
34+ the software.
35+ </ p >
36+
37+ < p >
38+ A well-written README makes it easier for developers and contributors
39+ to understand and work with a project.
40+ </ p >
41+
42+ < a
43+ href ="https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/ "
44+ target ="_blank "
45+ rel ="noopener noreferrer "
46+ >
47+ Learn more about README files
48+ </ a >
49+ </ article >
50+
51+ < article >
52+ < img src ="wireframe.png " alt ="Website wireframe example ">
53+
54+ < h2 > What is a Wireframe?</ h2 >
55+
56+ < p >
57+ A wireframe is a simple visual representation of a webpage or
58+ application. It focuses on structure and layout rather than colours,
59+ images or final design elements.
60+ </ p >
61+
62+ < p >
63+ Fun fact: designers also use wireframes to plan where content, navigation
64+ and key features will appear before development begins.
65+ </ p >
66+
67+ < a
68+ href ="https://balsamiq.com/blog/what-are-wireframes/ "
69+ target ="_blank "
70+ rel ="noopener noreferrer "
71+ >
72+ Learn more about wireframes
73+ </ a >
74+ </ article >
75+
76+ < article >
77+ < img src ="git-branch.png " alt ="Git branch diagram ">
78+
79+ < h2 > What is a Git Branch?</ h2 >
80+
81+ < p >
82+ A Git branch is an independent line of development within a Git
83+ repository. It allows developers to work on new features, bug fixes
84+ or experiments without affecting the main version of the project.
85+ </ p >
86+
87+ < p >
88+ Once the work is complete and tested, the branch can be merged back
89+ into the main codebase.
90+ </ p >
91+
92+ < a
93+ href ="https://www.atlassian.com/git/tutorials/using-branches "
94+ target ="_blank "
95+ rel ="noopener noreferrer "
96+ >
97+ Learn more about Git branches
98+ </ a >
99+ </ article >
100+ </ main >
103101
104102 < footer >
105103 < p > Created for CYF Wireframe assessment by Juanita Nwachukwu.</ p >
0 commit comments