|
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 Webcode Assignment</title> |
7 | 7 | <link rel="stylesheet" href="style.css" /> |
8 | 8 | </head> |
9 | 9 | <body> |
10 | 10 | <header> |
11 | 11 | <h1>Wireframe</h1> |
12 | 12 | <p> |
13 | | - This is the default, provided code and no changes have been made yet. |
| 13 | + This is the initial DRAFT version of this page. <!--First line updated to reflect draft status--> |
14 | 14 | </p> |
15 | 15 | </header> |
16 | 16 | <main> |
17 | 17 | <article> |
18 | 18 | <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 19 | + <h2>Wireframe schematic</h2> |
20 | 20 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 21 | + Wireframe is a visual guide that represents the skeletal framework |
| 22 | + of a website or application. Its purpose is to outline the layout. |
23 | 23 | </p> |
24 | 24 | <a href="">Read more</a> |
25 | | - </article> |
26 | | - </main> |
27 | | - <footer> |
28 | | - <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
30 | | - </p> |
| 25 | + </article> <<!--What is the purpose of a Wireframe--> |
| 26 | + <h3>What is the Purpose of a Readme File</h3> |
| 27 | + </main> |
| 28 | + <p> |
| 29 | + A readme file serves as a guide for users and developers, providing |
| 30 | + essential information about a project, including its purpose, |
| 31 | + installation instructions, usage guidelines, and contribution |
| 32 | + protocols. It helps ensure that everyone involved understands how to |
| 33 | + effectively use and contribute to the project. |
| 34 | + </p> |
| 35 | + <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more, Github Document</a> |
| 36 | + </article> <<!--What is the purpose of a Wireframe--> |
| 37 | + <h4>What is the Purpose of a Wireframe</h4> |
| 38 | + </main> |
| 39 | + <p> |
| 40 | + A wireframe is a visual guide that represents the skeletal framework |
| 41 | + of a website or application. Its purpose is to outline the layout, |
| 42 | + structure, and functionality of a page before the actual design and |
| 43 | + development process begins. Wireframes help stakeholders visualize |
| 44 | + the user interface, plan content placement, and ensure that the user |
| 45 | + experience is intuitive and effective. |
| 46 | + </p> |
| 47 | + <a href="https://www.productplan.com/glossary/wireframe/">Read more about Wireframes</a> |
| 48 | + </article> <<!--What is a branch in Git--> |
| 49 | + <h5>What is a branch in Git</h5> |
| 50 | + </main> |
| 51 | + <p> |
| 52 | + A branch in Git is a separate line of development that allows |
| 53 | + multiple versions of a project to coexist. It enables developers to |
| 54 | + work on new features, bug fixes, or experiments without affecting the |
| 55 | + main codebase. Branches facilitate collaboration, as team members can |
| 56 | + work independently and later merge their changes back into the main |
| 57 | + branch when ready. |
| 58 | + </p> |
| 59 | + <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">Read more about Git branches</a> |
31 | 60 | </footer> |
32 | 61 | </body> |
33 | 62 | </html> |
0 commit comments