|
1 | | -<!DOCTYPE html> |
| 1 | +<!doctype html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
|
10 | 10 | <header> |
11 | 11 | <h1>Wireframe</h1> |
12 | 12 | <p> |
13 | | - Wireframe is low-fidelity, Visual Blueprint of a webpage or app interface. |
| 13 | + Wireframe is low-fidelity, Visual Blueprint of a webpage or app |
| 14 | + interface. |
14 | 15 | </p> |
15 | 16 | </header> |
16 | | - <main> |
17 | | - <!-- what is the purpose of README article --> |
| 17 | + <main> |
| 18 | + <!-- what is the purpose of README article --> |
18 | 19 | <article> |
19 | | - <img src="https://www.makeareadme.com/images/open-graph-logo.png?v=20181203" alt="README image" /> |
| 20 | + <img |
| 21 | + src="https://www.makeareadme.com/images/open-graph-logo.png?v=20181203" |
| 22 | + alt="README image" |
| 23 | + /> |
20 | 24 | <h2>README file</h2> |
21 | | - <details> |
| 25 | + <details> |
22 | 26 | <summary> |
23 | | - The purpose of README file is to give information about the project and how to use it |
24 | | - </summary> |
25 | | - <p> A README file is the "front door" of your project. it is typically a text file (usuallyREADME.md using Markdown) located in the root directory of your code</p> |
26 | | - </details> |
27 | | - <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a> |
| 27 | + The purpose of README file is to give information about the project |
| 28 | + and how to use it |
| 29 | + </summary> |
| 30 | + <p> |
| 31 | + A README file is the "front door" of your project. it is typically a |
| 32 | + text file (usuallyREADME.md using Markdown) located in the root |
| 33 | + directory of your code |
| 34 | + </p> |
| 35 | + </details> |
| 36 | + <a |
| 37 | + href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes" |
| 38 | + >Read more</a |
| 39 | + > |
| 40 | + </article> |
| 41 | + <!--purpose of wireframe article--> |
| 42 | + <article> |
| 43 | + <img |
| 44 | + src="https://github.com/Dagim-Daniel/Module-Onboarding/blob/main/Wireframe/wireframe.png?raw=true" |
| 45 | + alt="" |
| 46 | + /> |
| 47 | + <h2>Purpose of Wireframe</h2> |
| 48 | + <details> |
| 49 | + <summary>It establish the basic Structure of a page.</summary> |
| 50 | + <p> |
| 51 | + wireframe is the perfect way for the designers to gauge how the user |
| 52 | + would interact with the interface. Before adding visual |
| 53 | + considerations like color or images, they serve as an outline to get |
| 54 | + the team on the same page early. |
| 55 | + </p> |
| 56 | + </details> |
| 57 | + <a href="https://medium.com/design-bootcamp/wireframes-5d63f9d760a8" |
| 58 | + >Read more</a |
| 59 | + > |
| 60 | + </article> |
| 61 | + <!-- what is branch git article --> |
| 62 | + <article> |
| 63 | + <img |
| 64 | + src="https://cdn.iconscout.com/icon/free/png-256/free-git-branch-logo-icon-svg-download-png-1982843.png" |
| 65 | + alt="" |
| 66 | + /> |
| 67 | + <h2>Branch in Git</h2> |
| 68 | + <details> |
| 69 | + <summary> |
| 70 | + In Git, branch a pointer to a snapshot of your changes. |
| 71 | + </summary> |
| 72 | + <p> |
| 73 | + Branch is like a separate working copy of your project in Git. It |
| 74 | + allows you to make changes without affecting the main branch (often |
| 75 | + called "main" or "master"). |
| 76 | + </p> |
| 77 | + </details> |
| 78 | + <a href="https://www.w3schools.com/git/git_branch.asp">Read more</a> |
28 | 79 | </article> |
29 | | - <!--purpose of wireframe article--> |
30 | | - <article> |
31 | | - <img src="https://github.com/Dagim-Daniel/Module-Onboarding/blob/main/Wireframe/wireframe.png?raw=true" alt=""> |
32 | | - <h2>Purpose of Wireframe</h2> |
33 | | - <details> |
34 | | - <summary> |
35 | | - It establish the basic Structure of a page. |
36 | | - </summary> |
37 | | - <p>wireframe is the perfect way for the designers to gauge how the user would interact with the interface. Before adding visual considerations like color or images, they serve as an outline to get the team on the same page early.</p> |
38 | | - </details> |
39 | | - <a href="https://medium.com/design-bootcamp/wireframes-5d63f9d760a8">Read more</a> |
40 | | - </article> |
41 | | - <!-- what is branch git article --> |
42 | | - <article> |
43 | | - <img src="https://cdn.iconscout.com/icon/free/png-256/free-git-branch-logo-icon-svg-download-png-1982843.png" alt=""> |
44 | | - <h2>Branch in Git</h2> |
45 | | - <details> |
46 | | - <summary> |
47 | | - In Git, branch a pointer to a snapshot of your changes. |
48 | | - </summary> |
49 | | - <p>Branch is like a separate working copy of your project in Git. It allows you to make changes without affecting the main branch (often called "main" or "master").</p> |
50 | | - </details> |
51 | | - <a href="https://www.w3schools.com/git/git_branch.asp">Read more</a> |
52 | | - </article> |
53 | 80 | </main> |
54 | 81 | <footer> |
55 | | - <p>Author: Dagim Daniel : <a href= "mailto:dagimdan19@gmail.com">dagimdan19@gmail.com</a></p> |
| 82 | + <p> |
| 83 | + Author: Dagim Daniel : |
| 84 | + <a href="mailto:dagimdan19@gmail.com">dagimdan19@gmail.com</a> |
| 85 | + </p> |
56 | 86 | </footer> |
57 | 87 | </body> |
58 | 88 | </html> |
0 commit comments