|
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 | | - <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
14 | | - </p> |
| 13 | + <p>Learn about README files, wireframes, and Git branches.</p> |
15 | 14 | </header> |
| 15 | + |
16 | 16 | <main> |
17 | 17 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 18 | + <img |
| 19 | + src="readme.png" |
| 20 | + alt="Illustration promoting the creation of an effective README file" |
| 21 | + /> |
| 22 | + <h2>What is a README File?</h2> |
| 23 | + <p> |
| 24 | + A README file explains what a project does, how to install it, how to |
| 25 | + use it, and any important information developers need. It is usually |
| 26 | + the first file people read when viewing a project. |
| 27 | + </p> |
| 28 | + <a href="https://www.makeareadme.com/">Read more</a> |
| 29 | + </article> |
| 30 | + |
| 31 | + <article> |
| 32 | + <img src="wireframe.png" alt="Wireframe showing a webpage layout" /> |
| 33 | + <h2>What is a Wireframe?</h2> |
| 34 | + <p> |
| 35 | + A wireframe is a digital diagram that shows the skeleton of a website. |
| 36 | + It strips away visual elements like colors, fonts, and images to focus |
| 37 | + entirely on where headers and content blocks live. |
| 38 | + </p> |
| 39 | + <a href="https://balsamiq.com/blog/what-are-wireframes/">Read more</a> |
| 40 | + </article> |
| 41 | + |
| 42 | + <article> |
| 43 | + <img src="git-branch.png" alt="Illustration of branching in Git" /> |
| 44 | + <h2>What is a Git Branch?</h2> |
20 | 45 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 46 | + A branch in Git is an independent line of development. Branches allow |
| 47 | + developers to work on new features or fixes without affecting the main |
| 48 | + project. |
23 | 49 | </p> |
24 | | - <a href="">Read more</a> |
| 50 | + <a |
| 51 | + href="https://book.the-turing-way.org/reproducible-research/vcs/vcs-git-branches/" |
| 52 | + >Read more</a |
| 53 | + > |
25 | 54 | </article> |
26 | 55 | </main> |
27 | 56 | <footer> |
|
0 commit comments