|
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 | + <meta |
| 8 | + name="description" |
| 9 | + content="Webpage explaining the purposes of a README file, Wireframe and Git Branches." |
| 10 | + /> |
7 | 11 | <link rel="stylesheet" href="style.css" /> |
8 | 12 | </head> |
9 | 13 | <body> |
10 | 14 | <header> |
11 | 15 | <h1>Wireframe</h1> |
12 | 16 | <p> |
13 | | - Webpage explaining the purposes of a README file, wireframe and a branch |
14 | | - in Git. |
| 17 | + Webpage explaining the purposes of a README file, Wireframe and Git |
| 18 | + Branches. |
15 | 19 | </p> |
16 | 20 | </header> |
17 | 21 | <main> |
18 | 22 | <section> |
19 | 23 | <article> |
20 | | - <img src="placeholder.svg" alt="" /> |
| 24 | + <img |
| 25 | + src="https://freerangestock.com/thumbnail/119557/web-developer--web-development--programmer--programming.jpg" |
| 26 | + alt="web-developer" |
| 27 | + width="200" |
| 28 | + height="350" |
| 29 | + loading="lazy" |
| 30 | + /> |
21 | 31 | <h2>README file</h2> |
22 | 32 | <p> |
23 | 33 | A README file is a document that provides information about a |
24 | 34 | project, such as its purpose, how to use it, and any other relevant |
25 | 35 | details. It is usually the first thing people read to understand the |
26 | 36 | project. |
27 | 37 | </p> |
28 | | - <a href="https://en.wikipedia.org/wiki/README">Read More </a> |
| 38 | + <a href="https://en.wikipedia.org/wiki/README" |
| 39 | + >Read More about README files</a |
| 40 | + > |
29 | 41 | </article> |
30 | 42 | </section> |
31 | 43 | <section> |
32 | 44 | <article> |
33 | | - <img src="placeholder.svg" alt="" /> |
| 45 | + <img |
| 46 | + src="https://freerangestock.com/thumbnail/130564/website-wireframe.jpg" |
| 47 | + alt="wireframe example" |
| 48 | + width="200" |
| 49 | + height="250" |
| 50 | + loading="lazy" |
| 51 | + /> |
34 | 52 | <h2>Wireframe</h2> |
35 | 53 | <p> |
36 | 54 | A wireframe is a visual guide that represents the skeletal structure |
37 | 55 | of a website or application. It outlines the layout, content, and |
38 | 56 | functionality without the final design elements. |
39 | 57 | </p> |
40 | | - <a href="">Read more</a> |
| 58 | + <a href="https://en.wikipedia.org/wiki/Wireframe" |
| 59 | + >Read more about Wireframes</a |
| 60 | + > |
41 | 61 | </article> |
42 | 62 | </section> |
43 | 63 | <section> |
44 | 64 | <article> |
45 | | - <img src="placeholder.svg" alt="" /> |
| 65 | + <img |
| 66 | + src="https://images.unsplash.com/photo-1556075798-4825dfaaf498?q=80&w=1476&auto=format&fit=crop&ixlib=rb-4.1.0&ixid=M3wxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D.jpg" |
| 67 | + alt="branches in development project" |
| 68 | + width="200" |
| 69 | + height="250" |
| 70 | + loading="lazy" |
| 71 | + /> |
46 | 72 | <h2>Branch in Git</h2> |
47 | 73 | <p> |
48 | 74 | A branch in Git is a separate line of development that allows you to |
49 | 75 | work on different features. It enables multiple developers to |
50 | 76 | collaborate on a project without interfering with each other's work. |
51 | 77 | </p> |
52 | | - <a href="https://en.wikipedia.org/wiki/Git_branch">Read more</a> |
| 78 | + <a href="https://en.wikipedia.org/wiki/Branching_(version_control)" |
| 79 | + >Read more about Git branches</a |
| 80 | + > |
53 | 81 | </article> |
54 | 82 | </section> |
55 | 83 | </main> |
|
0 commit comments