|
1 | | -<!DOCTYPE html> |
| 1 | +<!doctype html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
5 | 5 | <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
6 | 6 | <title>Wireframe</title> |
7 | 7 | <link rel="stylesheet" href="style.css" /> |
8 | 8 | </head> |
| 9 | + |
9 | 10 | <body> |
10 | 11 | <header> |
11 | 12 | <h1>Wireframe</h1> |
12 | 13 | <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
| 14 | + A wireframe is a simple visual blueprint or sketch of a webpage or |
| 15 | + application. |
14 | 16 | </p> |
15 | 17 | </header> |
| 18 | + |
16 | 19 | <main> |
17 | 20 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 21 | + <img src="mokey.jpg" alt="image of an upside down monkey" /> |
| 22 | + <h2>What is a README File?</h2> |
20 | 23 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 24 | + A README file provides information about a project, including its |
| 25 | + purpose, installation instructions, and how to use it. |
23 | 26 | </p> |
24 | | - <a href="">Read more</a> |
| 27 | + <a href="https://en.wikipedia.org/wiki/README" |
| 28 | + >Learn more about README files</a |
| 29 | + > |
| 30 | + </article> |
| 31 | + |
| 32 | + <article> |
| 33 | + <img src="bird.jpg" alt="An image of a black bird" /> |
| 34 | + <h2>What is a Wireframe?</h2> |
| 35 | + <p> |
| 36 | + A wireframe is a visual guide that helps designers and developers plan |
| 37 | + the structure and layout of a webpage before building it. |
| 38 | + </p> |
| 39 | + <a href="https://www.productplan.com/glossary/wireframe/" |
| 40 | + >Learn more about wireframes</a |
| 41 | + > |
| 42 | + </article> |
| 43 | + |
| 44 | + <article> |
| 45 | + <img |
| 46 | + src="Classroom Wireframe.jpg" |
| 47 | + alt="an image of a glass building" |
| 48 | + /> |
| 49 | + <h2>What is a Git Branch?</h2> |
| 50 | + <p> |
| 51 | + A Git branch allows developers to work on new features or fixes |
| 52 | + separately from the main project without affecting existing code. |
| 53 | + </p> |
| 54 | + <a |
| 55 | + href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" |
| 56 | + >Learn more about Git branches</a |
| 57 | + > |
25 | 58 | </article> |
26 | 59 | </main> |
| 60 | + |
27 | 61 | <footer> |
28 | | - <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
30 | | - </p> |
| 62 | + <p>Enice Mutanda 2026 CYF</p> |
31 | 63 | </footer> |
32 | 64 | </body> |
33 | 65 | </html> |
0 commit comments