1- < body >
2- < header >
3- < h1 > Web Development Fundamentals</ h1 >
4- < p >
5- An introduction to README files, wireframes, and Git branches.
6- </ p >
7- </ header >
1+ <!DOCTYPE html>
2+ < html lang ="en ">
3+ < head >
4+ < meta charset ="UTF-8 " />
5+ < meta name ="viewport " content ="width=device-width, initial-scale=1.0 " />
6+ < title > Web Fundamentals</ title >
7+ < link rel ="stylesheet " href ="style.css " />
8+ </ head >
89
9- < main >
10- < article >
11- < img src ="placeholder.svg " alt ="Document icon representing a README file " />
12- < h2 > What is a README file?</ h2 >
13- < p >
14- A README file explains what a project does, how to set it up, and how to
15- use or contribute to it. It is usually the first thing people read when
16- they open a repository.
17- </ p >
18- < a href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes ">
19- Learn more about README files
20- </ a >
21- </ article >
10+ < body >
11+ < header >
12+ < h1 > Web Fundamentals!!!</ h1 >
13+ < p > Understanding README files, wireframes, and Git branches</ p >
14+ </ header >
2215
23- < article >
24- < img src ="placeholder.svg " alt ="Wireframe sketch showing webpage layout " />
25- < h2 > What is a wireframe?</ h2 >
26- < p >
27- A wireframe is a simple visual guide that shows the structure and layout
28- of a webpage before it is built. It helps designers and developers plan
29- content placement and user flow.
30- </ p >
31- < a href ="https://www.productplan.com/glossary/wireframe/ ">
32- Learn more about wireframes
33- </ a >
34- </ article >
16+ < main >
17+ <!-- Featured article (top wide card) -->
18+ < article class ="featured ">
19+ < img
20+ src ="placeholder.svg "
21+ alt ="Document icon representing a README file "
22+ />
23+ < h2 > What is a README file?</ h2 >
24+ < p >
25+ A README file explains what a project is, how to install or run it,
26+ and how others can use or contribute to it. It is usually the first
27+ file someone reads in a repository.
28+ </ p >
29+ < a
30+ href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes "
31+ >
32+ Read more
33+ </ a >
34+ </ article >
3535
36- < article >
37- < img src ="placeholder.svg " alt ="Diagram showing Git branches " />
38- < h2 > What is a Git branch?</ h2 >
39- < p >
40- A Git branch is a separate line of development that allows developers to
41- work on features or fixes without affecting the main codebase until the
42- changes are ready.
43- </ p >
44- < a href ="https://git-scm.com/docs/git-branch ">
45- Learn more about Git branches
46- </ a >
47- </ article >
48- </ main >
36+ <!-- Two smaller articles -->
37+ < article >
38+ < img
39+ src ="placeholder.svg "
40+ alt ="Wireframe sketch showing page layout "
41+ />
42+ < h2 > What is a wireframe?</ h2 >
43+ < p >
44+ A wireframe is a simple visual guide that shows the structure and
45+ layout of a webpage before any code is written.
46+ </ p >
47+ < a href ="https://www.productplan.com/glossary/wireframe/ ">
48+ Read more
49+ </ a >
50+ </ article >
4951
50- < footer >
51- < p > © 2026 Ziad Ahmed</ p >
52- </ footer >
53- </ body >
54- s
52+ < article >
53+ < img
54+ src ="placeholder.svg "
55+ alt ="Diagram illustrating Git branches "
56+ />
57+ < h2 > What is a Git branch?</ h2 >
58+ < p >
59+ A Git branch allows developers to work on new features or fixes in
60+ isolation without affecting the main codebase.
61+ </ p >
62+ < a href ="https://git-scm.com/docs/git-branch ">
63+ Read more
64+ </ a >
65+ </ article >
66+ </ main >
67+
68+ < footer >
69+ < p > © 2026 Ziad Ahmed</ p >
70+ </ footer >
71+ </ body >
72+ </ html >
0 commit comments