|
8 | 8 | </head> |
9 | 9 | <body> |
10 | 10 | <header> |
11 | | - <h1>Read me</h1> |
| 11 | + <h1>Wireframe</h1> |
| 12 | + </header> |
| 13 | + |
| 14 | + <main class="article-container" method="GET"> |
| 15 | + <article> |
| 16 | + <img src="placeholder.svg" alt="placeholder image" /> |
| 17 | + <h2>Purpose of a readme file</h2> |
12 | 18 | <p> |
13 | | - A README file is the first thing people see when they open a code repository. |
14 | | - Its main purpose is to explain what the project is and how to use it. |
| 19 | + A readme file is a document that provides information about a project, |
| 20 | + including its purpose, how to use it, and any other relevant details. |
| 21 | + It serves as a guide for users and developers who may be interested in the project. |
15 | 22 | </p> |
16 | | - </header> |
17 | | - <main> |
| 23 | + <a href="https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/" target="_blank">Read more </a> |
| 24 | + </article> |
| 25 | + |
18 | 26 | <article> |
19 | | - <img src="placeholder.svg" alt="" /> |
20 | | - <h2>Wireframe</h2> |
| 27 | + <img src="placeholder.svg" alt="placeholder image" /> |
| 28 | + <h2>Purpose of a wireframe</h2> |
21 | 29 | <p> |
22 | | - A wireframe is like the blueprint of a house, |
23 | | - but for a website or an app. It is a simple, |
24 | | - black-and-white sketch that shows where things go before you start building. |
| 30 | + A wireframe is a visual representation of a website or application's layout and structure. |
| 31 | + It shows the placement of elements, such as text, images, and buttons, without the final design details. |
| 32 | + Wireframes are used to plan and communicate the basic structure and functionality of a product before development begins. |
25 | 33 | </p> |
26 | | - <h3>Branch in Git</h3> |
| 34 | + <a href="https://www.freecodecamp.org/news/how-to-create-a-wireframe/" target="_blank">Read more </a> |
| 35 | + </article> |
| 36 | + |
| 37 | + <article> |
| 38 | + <img src="placeholder.svg" alt="placeholder image" /> |
| 39 | + <h2>what is a Branch in a Git</h2> |
27 | 40 | <p> |
28 | | - A branch in Git is an independent line of development. |
29 | | - It acts as a pointer to a specific commit, |
30 | | - allowing you to work on new features, bug fixes, |
31 | | - or experiments without affecting the main, |
32 | | - stable codebase (usually called main or master). |
| 41 | + A branch in Git is a separate line of development that allows you to work on different features or bug fixes without affecting the main codebase. |
| 42 | + It enables multiple developers to collaborate on a project simultaneously and helps manage changes effectively. |
| 43 | + Branches can be merged back into the main branch once the work is complete and tested. |
33 | 44 | </p> |
34 | | - <a href="">Read more</a> |
| 45 | + <a href="https://www.freecodecamp.org/news/what-is-a-git-branch/" target="_blank">Read more </a> |
35 | 46 | </article> |
36 | | - </main> |
37 | | - <footer> |
38 | | - <p> |
39 | | - this is a footer. It usually contains information about the website, |
40 | | - </p> |
41 | | - </footer> |
| 47 | + </main> |
| 48 | + |
| 49 | + <footer> |
| 50 | + <p>© 2026 Professional Web Developer Assignment</p> |
| 51 | + </footer> |
42 | 52 | </body> |
43 | | -</html> |
| 53 | + |
0 commit comments