|
1 | | -<!DOCTYPE html> |
| 1 | +<!doctype html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
|
9 | 9 | <body> |
10 | 10 | <header> |
11 | 11 | <h1>Exploring README Files, Wireframes and Git Branches</h1> |
12 | | - <p>We will be looking at the purposes and benefits of README files, Wireframes and Git Branches</p> |
| 12 | + <p> |
| 13 | + We will be looking at the purposes and benefits of README files, |
| 14 | + Wireframes and Git Branches |
| 15 | + </p> |
13 | 16 | </header> |
14 | 17 | <main> |
15 | 18 | <article> |
16 | | - <img src="https://static0.makeuseofimages.com/wordpress/wp-content/uploads/2023/08/readme-article.jpg?q=50&fit=crop&w=1488&h=837&dpr=1.5" alt="readme image" /> |
| 19 | + <img |
| 20 | + src="https://static0.makeuseofimages.com/wordpress/wp-content/uploads/2023/08/readme-article.jpg?q=50&fit=crop&w=1488&h=837&dpr=1.5" |
| 21 | + alt="readme image" |
| 22 | + /> |
17 | 23 | <h2>README Files</h2> |
18 | 24 | <p> |
19 | | - The purpose of a README file is to serve as the primary guide and entry point for a project, |
20 | | - dataset, or software. It communicates what the project does, how to install and use it, |
21 | | - how to contribute, and provides context so that others can easily understand or interact with the content. |
| 25 | + The purpose of a README file is to serve as the primary guide and |
| 26 | + entry point for a project, dataset, or software. It communicates what |
| 27 | + the project does, how to install and use it, how to contribute, and |
| 28 | + provides context so that others can easily understand or interact with |
| 29 | + the content. |
22 | 30 | </p> |
23 | | - <a href="https://www.makeuseof.com/readme-files-how-to-write-the-best/">Read more</a> |
| 31 | + <a href="https://www.makeuseof.com/readme-files-how-to-write-the-best/" |
| 32 | + >Read more</a |
| 33 | + > |
24 | 34 | </article> |
25 | 35 | <article> |
26 | | -<img src="https://miro.medium.com/v2/resize:fit:1100/format:webp/1*bl0mLTGKrUfdIPS0hSKUBA.jpeg" alt="wireframe image"> |
27 | | - <h2>Wireframes</h2> |
28 | | - <p>The primary purpose of a wireframe is to act as a visual blueprint. |
29 | | - It establishes the basic structure, content placement, and core |
30 | | - functionality of a digital product before visual design and coding begin. |
31 | | - </p> |
32 | | - <a href="https://balsamiq.com/blog/what-are-wireframes/">Read more</a> |
33 | | - </article> |
| 36 | + <img |
| 37 | + src="https://miro.medium.com/v2/resize:fit:1100/format:webp/1*bl0mLTGKrUfdIPS0hSKUBA.jpeg" |
| 38 | + alt="wireframe image" |
| 39 | + /> |
| 40 | + <h2>Wireframes</h2> |
| 41 | + <p> |
| 42 | + The primary purpose of a wireframe is to act as a visual blueprint. It |
| 43 | + establishes the basic structure, content placement, and core |
| 44 | + functionality of a digital product before visual design and coding |
| 45 | + begin. |
| 46 | + </p> |
| 47 | + <a href="https://balsamiq.com/blog/what-are-wireframes/">Read more</a> |
| 48 | + </article> |
34 | 49 | <article> |
35 | | - |
36 | | - <img src="https://hpc-wiki.info/mediawiki/hpc_images/thumb/6/6d/Git_tutorial_-_branching.png/700px-Git_tutorial_-_branching.png" alt="git branch image"> |
37 | | -<h2>Git Branches</h2> |
38 | | -<p> |
39 | | - In Git, a branch is essentially a lightweight, movable pointer to a specific commit in your |
40 | | - repository's history. Conceptually, it serves as an isolated, parallel workspace where |
41 | | - you can develop new features, fix bugs, or experiment without affecting the stable "main" code. |
42 | | -</p> |
43 | | -<a href="https://miro.medium.com/v2/resize:fit:1100/format:webp/1*bl0mLTGKrUfdIPS0hSKUBA.jpeg">Read more</a> |
| 50 | + <img |
| 51 | + src="https://hpc-wiki.info/mediawiki/hpc_images/thumb/6/6d/Git_tutorial_-_branching.png/700px-Git_tutorial_-_branching.png" |
| 52 | + alt="git branch image" |
| 53 | + /> |
| 54 | + <h2>Git Branches</h2> |
| 55 | + <p> |
| 56 | + In Git, a branch is essentially a lightweight, movable pointer to a |
| 57 | + specific commit in your repository's history. Conceptually, it serves |
| 58 | + as an isolated, parallel workspace where you can develop new features, |
| 59 | + fix bugs, or experiment without affecting the stable "main" code. |
| 60 | + </p> |
| 61 | + <a |
| 62 | + href="https://miro.medium.com/v2/resize:fit:1100/format:webp/1*bl0mLTGKrUfdIPS0hSKUBA.jpeg" |
| 63 | + >Read more</a |
| 64 | + > |
44 | 65 | </article> |
45 | 66 | </main> |
46 | 67 | <footer> |
47 | | - <p> |
48 | | - email: taliakucuk1@gmail.com |
49 | | - </p> |
| 68 | + <p>email: taliakucuk1@gmail.com</p> |
50 | 69 | </footer> |
51 | 70 | </body> |
52 | 71 | </html> |
0 commit comments