|
8 | 8 | </head>
|
9 | 9 | <body>
|
10 | 10 | <header>
|
11 |
| - <h1>Wireframe</h1> |
12 |
| - <p> |
13 |
| - This is the default, provided code and no changes have been made yet. |
14 |
| - </p> |
| 11 | + <h1>What is a Wireframe</h1> |
| 12 | + <p id="wireframe-definition"> |
| 13 | + A <strong>wireframe</strong> is a visual representation of a user interface, |
| 14 | + often used in the early stages of design to outline the structure and layout of a website or application. |
| 15 | + </p> |
15 | 16 | </header>
|
16 | 17 | <main>
|
17 |
| - <article> |
18 |
| - <img src="placeholder.svg" alt="" /> |
19 |
| - <h2>Title</h2> |
20 |
| - <p> |
21 |
| - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 |
| - voluptates. Quisquam, voluptates. |
| 18 | + <article class="wireframe-purpose"> |
| 19 | + <img src="https://support.microsoft.com/images/en-us/ae7333a6-5681-45ea-b482-e0de7c81cabd" alt="A basic wireframe layout" width="200" /> |
| 20 | + <h4>What is the purpose of a wireframe?</h4> |
| 21 | + <p id="wireframe-purpose"> |
| 22 | + A <strong>wireframe</strong> serves as a visual guide that represents the skeletal framework of a website or application. |
| 23 | + The primary purpose of a <strong>wireframe</strong> is to establish the basic structure and layout of a website |
| 24 | + or application before visual design and content are added. It acts as a blueprint, outlining the |
| 25 | + placement of elements like headings, paragraphs, images, buttons, and navigation. Wireframes help designers, developers, |
| 26 | + and stakeholders visualize the user experience and identify potential issues early in the project. |
| 27 | + </p> |
| 28 | + <a href="https://www.experienceux.co.uk/faqs/what-is-wireframing/">Read more</a> |
| 29 | + </article> |
| 30 | + <article id="readme-file"> |
| 31 | + <img src="https://miro.medium.com/v2/resize:fit:1400/1*8aBw4cfLAYJwbBnFQC_JCg.png" alt="README File" /> |
| 32 | + <h4>What is the README File?</h4> |
| 33 | + <p class="readme-file"> |
| 34 | + A <strong>README</strong> file is a text file that <br> information about a project. |
| 35 | + It is typically included in the root directory of a <br>project |
| 36 | + and is often the first file that users see when they access the project,<br> |
| 37 | + providing users with essential information about the <br>project, |
| 38 | + its purpose, how to use it, and where to find help or support.<br> |
| 39 | + It's often the first thing someone will see when they access a project, |
| 40 | + making it a crucial tool for communication and documentation.<br> |
| 41 | + A well-structured <strong>README</strong> file can help users understand the project quickly and effectively.<br> |
| 42 | + <br> |
| 43 | + A typical README file might include:<br> |
| 44 | + Project Overview,Installation Instructions,Usage Examples,Contribution Guidelines,Troubleshooting,Changelog.<br> |
| 45 | + <br> |
| 46 | + <strong>README</strong> files are often written in Markdown, a lightweight markup language that allows for easy formatting.<br> |
| 47 | + </p> |
| 48 | + <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a> |
| 49 | + </article> |
| 50 | + |
| 51 | + <article id="git-branch"> |
| 52 | + <img src="https://miro.medium.com/v2/resize:fit:650/1*K9scAx1Ezd-KJFabaYseCw.jpeg" alt="Git-Branch" /> |
| 53 | + <h4>What is a branch in Git?</h4> |
| 54 | + <p class="git-branch"> |
| 55 | + A <strong>branch</strong> in Git is a pointer to a specific <br> |
| 56 | + commit in the repository's history. When you create a new branch,<br> |
| 57 | + you're essentially creating a new line of development that diverges<br> |
| 58 | + from the main line (usually the master branch).A branch in<br> |
| 59 | + <strong>Git</strong> is simply a lightweight movable pointer to one <br> |
| 60 | + of these commits.The default branch name in Git is <strong>master</strong>. As you <br> |
| 61 | + start making commits, you'regiven a master branch that points to the last commit you made. <br> |
| 62 | + Every time you commit,the master branch pointer moves forward automatically. Note.<br> |
23 | 63 | </p>
|
24 |
| - <a href="">Read more</a> |
| 64 | + <a href="https://www.w3schools.com/git/git_branch.asp">Read more</a> |
25 | 65 | </article>
|
26 | 66 | </main>
|
27 | 67 | <footer>
|
28 |
| - <p> |
29 |
| - This is the default, provided code and no changes have been made yet. |
| 68 | + <p id="footer-text"> |
| 69 | + © 2025 <a href="https://www.github.com">Houssam Lahlah</a> | |
| 70 | + <a href="https://www.codeyourfuture.com">CodeYourFuture</a> | All rights reserved. |
30 | 71 | </p>
|
31 | 72 | </footer>
|
32 | 73 | </body>
|
|
0 commit comments