|
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>Web Development Essentials</title> |
7 | 7 | <link rel="stylesheet" href="style.css" /> |
8 | 8 | </head> |
| 9 | + |
9 | 10 | <body> |
10 | 11 | <header> |
11 | | - <h1>Wireframe</h1> |
12 | | - <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
14 | | - </p> |
| 12 | + <h1>Web Development Essentials</h1> |
| 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="placeholder.svg" |
| 20 | + alt="Illustration representing a README file" |
| 21 | + /> |
| 22 | + |
| 23 | + <h2>What is a README File?</h2> |
| 24 | + |
| 25 | + <p> |
| 26 | + A README file introduces a project and explains its purpose. It often |
| 27 | + includes installation instructions, usage information, and other |
| 28 | + important details for developers and users. |
| 29 | + </p> |
| 30 | + |
| 31 | + <a |
| 32 | + href="https://en.wikipedia.org/wiki/README" |
| 33 | + target="_blank" |
| 34 | + rel="noopener noreferrer" |
| 35 | + > |
| 36 | + Read More |
| 37 | + </a> |
| 38 | + </article> |
| 39 | + |
| 40 | + <article> |
| 41 | + <img |
| 42 | + src="placeholder.svg" |
| 43 | + alt="Illustration representing a wireframe" |
| 44 | + /> |
| 45 | + |
| 46 | + <h2>What is a Wireframe?</h2> |
| 47 | + |
| 48 | + <p> |
| 49 | + A wireframe is a simple visual guide used to plan the layout of a web |
| 50 | + page. It helps designers and developers understand the structure of a |
| 51 | + site before building it. |
| 52 | + </p> |
| 53 | + |
| 54 | + <a |
| 55 | + href="https://www.productplan.com/glossary/wireframe/" |
| 56 | + target="_blank" |
| 57 | + rel="noopener noreferrer" |
| 58 | + > |
| 59 | + Read More |
| 60 | + </a> |
| 61 | + </article> |
| 62 | + |
| 63 | + <article> |
| 64 | + <img |
| 65 | + src="placeholder.svg" |
| 66 | + alt="Illustration representing Git branches" |
| 67 | + /> |
| 68 | + |
| 69 | + <h2>What is a Git Branch?</h2> |
| 70 | + |
20 | 71 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 72 | + A Git branch is an independent line of development. Branches allow |
| 73 | + developers to work on new features or fixes without affecting the main |
| 74 | + version of a project. |
23 | 75 | </p> |
24 | | - <a href="">Read more</a> |
| 76 | + |
| 77 | + <a |
| 78 | + href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" |
| 79 | + target="_blank" |
| 80 | + rel="noopener noreferrer" |
| 81 | + > |
| 82 | + Read More |
| 83 | + </a> |
25 | 84 | </article> |
26 | 85 | </main> |
| 86 | + |
27 | 87 | <footer> |
28 | 88 | <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
| 89 | + Made by Khaliun Baatarkhuu |
30 | 90 | </p> |
31 | 91 | </footer> |
32 | 92 | </body> |
|
0 commit comments