|
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
5 | 5 | <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
6 | | - <title>Wireframe</title> |
| 6 | + <title>Wireframe Exercise</title> |
7 | 7 | <link rel="stylesheet" href="style.css" /> |
8 | 8 | </head> |
| 9 | + |
9 | 10 | <body> |
10 | | - <header> |
11 | | - <h1>Wireframe</h1> |
12 | | - <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
14 | | - </p> |
15 | | - </header> |
16 | 11 | <main> |
| 12 | + <!-- Header MUST be first child of main for the CSS grid --> |
| 13 | + <header> |
| 14 | + <h1>Web Development Basics</h1> |
| 15 | + <p> |
| 16 | + This page explains the purpose of a README file, a wireframe, and a Git |
| 17 | + branch. |
| 18 | + </p> |
| 19 | + </header> |
| 20 | + |
| 21 | + <article> |
| 22 | + <img |
| 23 | + src="placeholder.svg" |
| 24 | + alt="Illustration representing a README file" |
| 25 | + /> |
| 26 | + <h2>Purpose of a README file</h2> |
| 27 | + <p> |
| 28 | + A README file explains what a project is, how it works, and how to use |
| 29 | + it. It helps other developers understand the project quickly. |
| 30 | + </p> |
| 31 | + <a |
| 32 | + href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes" |
| 33 | + > |
| 34 | + Read more |
| 35 | + </a> |
| 36 | + </article> |
| 37 | + |
| 38 | + <article> |
| 39 | + <img |
| 40 | + src="wireframe.png" |
| 41 | + alt="Illustration showing a wireframe layout" |
| 42 | + /> |
| 43 | + <h2>Purpose of a wireframe</h2> |
| 44 | + <p> |
| 45 | + A wireframe is a simple visual plan of a webpage. It shows the layout |
| 46 | + and structure before colours, images, or styling are added. |
| 47 | + </p> |
| 48 | + <a href="https://www.productplan.com/glossary/wireframe/"> |
| 49 | + Read more |
| 50 | + </a> |
| 51 | + </article> |
| 52 | + |
17 | 53 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 54 | + <img |
| 55 | + src="placeholder.svg" |
| 56 | + alt="Illustration representing a Git branch" |
| 57 | + /> |
| 58 | + <h2>What is a Git branch?</h2> |
20 | 59 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 60 | + A Git branch allows developers to work on changes safely without |
| 61 | + affecting the main code until the work is ready. |
23 | 62 | </p> |
24 | | - <a href="">Read more</a> |
| 63 | + <a |
| 64 | + href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" |
| 65 | + > |
| 66 | + Read more |
| 67 | + </a> |
25 | 68 | </article> |
26 | 69 | </main> |
| 70 | + |
27 | 71 | <footer> |
28 | | - <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
30 | | - </p> |
| 72 | + <p>© 2026 Web Basics</p> |
31 | 73 | </footer> |
32 | 74 | </body> |
33 | 75 | </html> |
0 commit comments