|
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>Basic of Web Development </h1> |
| 12 | + <P> |
| 13 | + Web development is the process of creating and maintaining websites and web applications.<br> |
| 14 | + Good web developers, they have a strong understanding of Git, README files and wireframes(Design) before the actual development process.<br> |
| 15 | + This articles introduce the purpose of README files,wireframes and how to create branches in Git. |
| 16 | + </P> |
| 17 | + |
15 | 18 | </header> |
16 | 19 | <main> |
17 | 20 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 21 | + |
| 22 | + <img src="image_readme.png" alt="README file illustration" /> |
| 23 | + <h2>Purpose of README file</h2> |
| 24 | + <p> |
| 25 | + README files to communicate important information about a project for users and developers. |
| 26 | + A README is often the first item a visitor will see when visiting your repository. |
| 27 | + From the readme, users can easily understand what your project is about, how to use it. |
| 28 | + </p> |
| 29 | + <p> |
| 30 | + README files typically include information on: |
| 31 | + <ul> |
| 32 | + <li>What the project does a Project description</li> |
| 33 | + <li>How users can get started with the project Installation instructions</li> |
| 34 | + <li>Usage guidelines</li> |
| 35 | + <li>Contributing guidelines</li> |
| 36 | + <li>License information</li> |
| 37 | + </p> |
| 38 | + <a href="purpose_readme.html">Read more</a> |
| 39 | + </article> |
| 40 | + <article> |
| 41 | + <img src="image_wireframe.png" alt="Wireframe Example" /> |
| 42 | + <h2>Purpose of a wireframe</h2> |
| 43 | + <p> |
| 44 | + Wireframe graphic representation of a website, mobile app, or other digital interface that highlights the overall structure and layout of the design without going into specifics like colors, fonts, or images. A wireframe is a product outline that shows what interface elements will be present on important pages. |
| 45 | + </p> |
| 46 | + <p> |
| 47 | + Wireframes are used to: |
| 48 | + <ul> |
| 49 | + |
| 50 | + <li>Structural Planning</li> |
| 51 | + <li>User Flow</li> |
| 52 | + <li>Communication</li> |
| 53 | + |
| 54 | + </ul> |
| 55 | + </p> |
| 56 | + <a href="purpose_wireframe.html">Read more</a> |
| 57 | + </article> |
| 58 | + <article> |
| 59 | + <img src="image_git.png" alt="branch in git" id="branch-image"/> |
| 60 | + <h2>Branch in Git</h2> |
20 | 61 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 62 | + In Git, a branch is like a separate workspace where you can make changes and try new ideas without affecting the main project. Think of it as a "parallel universe" for your code. |
23 | 63 | </p> |
24 | | - <a href="">Read more</a> |
| 64 | + <p> |
| 65 | + Common Reasons to Create a Branch: |
| 66 | + </p> |
| 67 | + <ul> |
| 68 | + <li>Developing a new feature</li> |
| 69 | + <li>Fixing a bug</li> |
| 70 | + <li>Experimenting with ideas</li> |
| 71 | + </ul> |
| 72 | + |
| 73 | + <a href="branch_git.html">Read more</a> |
25 | 74 | </article> |
26 | 75 | </main> |
27 | 76 | <footer> |
28 | 77 | <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
| 78 | + Contact: <a href="mailto:yonas.desbelegebre@gmail.com">yonas.desbelegebre@gmail.com</a> |
| 79 | + copyright © 2026 Yonas Gebre. All rights reserved. |
30 | 80 | </p> |
31 | 81 | </footer> |
32 | 82 | </body> |
|
0 commit comments