|
1 | 1 | <!DOCTYPE html> |
2 | 2 | <html lang="en"> |
3 | 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"> |
| 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 | 8 | </head> |
9 | 9 |
|
10 | 10 | <body> |
11 | | -<header> |
12 | | -<h1>Wireframe</h1> |
13 | | -</header> |
| 11 | + <header> |
| 12 | + <h1>Wireframe</h1> |
| 13 | + </header> |
14 | 14 |
|
15 | | -<main> |
16 | | -<section class="articles-container"> |
17 | | -<h2 class="visually-hidden">Core Web Development Articles</h2> |
| 15 | + <main> |
| 16 | + <section class="articles-container"> |
| 17 | + <h2 class="visually-hidden">Core Web Development Articles</h2> |
18 | 18 |
|
19 | | -<article> |
20 | | -<img src="./images/readme-concept.jpg" |
21 | | -alt="A laptop screen showing a project documentation file"> |
22 | | -<h3>What is the purpose of a README file?</h3> |
23 | | -<p> |
24 | | -A README file is the front page of a repository. It introduces the |
25 | | -project, explains how to install or run the code, and guides other |
26 | | -developers on how to contribute. |
27 | | -</p> |
28 | | -<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"> |
29 | | -Read more about READMEs |
30 | | -</a> |
31 | | -</article> |
| 19 | + <article> |
| 20 | + <img src="./images/readme-concept.jpg" |
| 21 | + alt="A laptop screen showing a project documentation file"> |
| 22 | + <h3>What is the purpose of a README file?</h3> |
| 23 | + <p> |
| 24 | + A README file is the front page of a repository. It introduces the |
| 25 | + project, explains how to install or run the code, and guides other |
| 26 | + developers on how to contribute. |
| 27 | + </p> |
| 28 | + <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"> |
| 29 | + Read more about READMEs |
| 30 | + </a> |
| 31 | + </article> |
32 | 32 |
|
33 | | -<article> |
34 | | -<img src="./images/wireframe-concept.jpg" |
35 | | -alt="A simple sketch of a website layout using lines and boxes"> |
36 | | -<h3>What is the purpose of a wireframe?</h3> |
37 | | -<p> |
38 | | -A wireframe acts as a blueprint for a user interface. It defines the |
39 | | -structural layout, content hierarchy, and functionality of a page |
40 | | -before any visual design or code is added. |
41 | | -</p> |
42 | | -<a href="https://en.wikipedia.org/wiki/Website_wireframe"> |
43 | | -Read more about Wireframes |
44 | | -</a> |
45 | | -</article> |
| 33 | + <article> |
| 34 | + <img src="./images/wireframe-concept.jpg" |
| 35 | + alt="A simple sketch of a website layout using lines and boxes"> |
| 36 | + <h3>What is the purpose of a wireframe?</h3> |
| 37 | + <p> |
| 38 | + A wireframe acts as a blueprint for a user interface. It defines the |
| 39 | + structural layout, content hierarchy, and functionality of a page |
| 40 | + before any visual design or code is added. |
| 41 | + </p> |
| 42 | + <a href="https://en.wikipedia.org/wiki/Website_wireframe"> |
| 43 | + Read more about Wireframes |
| 44 | + </a> |
| 45 | + </article> |
46 | 46 |
|
47 | | -<article> |
48 | | -<img src="./images/git-branch-concept.jpg" |
49 | | -alt="A diagram showing a main code branch splitting into a feature branch"> |
50 | | -<h3>What is a branch in Git?</h3> |
51 | | -<p> |
52 | | -A branch is an independent line of development in Git. It allows you |
53 | | -to work on new features or fixes safely without affecting the stable |
54 | | -'main' codebase until it is fully tested. |
55 | | -</p> |
56 | | -<a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell"> |
57 | | -Read more about Git Branches |
58 | | -</a> |
59 | | -</article> |
| 47 | + <article> |
| 48 | + <img src="./images/git-branch-concept.jpg" |
| 49 | + alt="A diagram showing a main code branch splitting into a feature branch"> |
| 50 | + <h3>What is a branch in Git?</h3> |
| 51 | + <p> |
| 52 | + A branch is an independent line of development in Git. It allows you |
| 53 | + to work on new features or fixes safely without affecting the stable |
| 54 | + 'main' codebase until it is fully tested. |
| 55 | + </p> |
| 56 | + <a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell"> |
| 57 | + Read more about Git Branches |
| 58 | + </a> |
| 59 | + </article> |
60 | 60 |
|
61 | | -</section> |
62 | | -</main> |
| 61 | + </section> |
| 62 | + </main> |
63 | 63 |
|
64 | | -<footer> |
65 | | -<p>© 2026 Code Your Future Onboarding Coursework. Created by Tiffany.</p> |
66 | | -</footer> |
| 64 | + <footer> |
| 65 | + <p>© 2026 Code Your Future Onboarding Coursework. Created by Tiffany.</p> |
| 66 | + </footer> |
67 | 67 | </body> |
68 | 68 | </html> |
69 | 69 |
|
0 commit comments