|
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>Code Hub</h1> |
12 | 12 | <p> |
13 | | - Learn to code with hands-on projects and expert guidance. Join our community of developers |
| 13 | + Learn to code with hands-on projects and expert guidance. Join our |
| 14 | + community of developers |
14 | 15 | </p> |
15 | 16 | </header> |
16 | 17 | <main> |
17 | 18 | <article> |
18 | | - <img src="Readme.png" alt="README file illustration"/> |
| 19 | + <img src="Readme.png" alt="README file illustration" /> |
19 | 20 | <h2>What is a README file?</h2> |
20 | 21 | <p class="intro"> |
21 | | - A README is the front door of any software project — the first document a visitor reads when they encounter your code. |
| 22 | + A README is the front door of any software project — the first |
| 23 | + document a visitor reads when they encounter your code. |
22 | 24 | </p> |
23 | 25 | <p class="content"> |
24 | | - Typically named README.md and written in Markdown, it lives at the root |
25 | | - of a repository and renders automatically on platforms like GitHub. Its core |
26 | | - purpose is to answer three questions immediately: what does this project do, |
27 | | - how do I get it running, and how do I use it?<br>A well-crafted README... |
| 26 | + Typically named README.md and written in Markdown, it lives at the |
| 27 | + root of a repository and renders automatically on platforms like |
| 28 | + GitHub. Its core purpose is to answer three questions immediately: |
| 29 | + what does this project do, how do I get it running, and how do I use |
| 30 | + it?<br />A well-crafted README... |
28 | 31 | </p> |
29 | | - <a href="https://en.wikipedia.org/wiki/README" target="_blank">Read more</a> |
| 32 | + <a href="https://en.wikipedia.org/wiki/README" target="_blank" |
| 33 | + >Read more</a |
| 34 | + > |
30 | 35 | </article> |
31 | 36 | <article> |
32 | | - <img src="Wireframe1.png" alt="Wireframe illustration"/> |
| 37 | + <img src="Wireframe1.png" alt="Wireframe illustration" /> |
33 | 38 | <h2>What is a WIREFRAME?</h2> |
34 | 39 | <p class="intro"> |
35 | | - A wireframe is a skeletal blueprint of a digital interface — a low-fidelity sketch that maps out layout and structure before any visual design begins. |
| 40 | + A wireframe is a skeletal blueprint of a digital interface — a |
| 41 | + low-fidelity sketch that maps out layout and structure before any |
| 42 | + visual design begins. |
36 | 43 | </p> |
37 | 44 | <p class="content"> |
38 | | - Think of it as the floor plan of a building: it shows where the rooms are, how they connect, and how large each space is — but says nothing about paint colours or furniture. In UI/UX design, wireframes... |
| 45 | + Think of it as the floor plan of a building: it shows where the rooms |
| 46 | + are, how they connect, and how large each space is — but says nothing |
| 47 | + about paint colours or furniture. In UI/UX design, wireframes... |
39 | 48 | </p> |
40 | | - <a href="https://en.wikipedia.org/wiki/Website_wireframe" target="_blank">Read more</a> |
| 49 | + <a |
| 50 | + href="https://en.wikipedia.org/wiki/Website_wireframe" |
| 51 | + target="_blank" |
| 52 | + >Read more</a |
| 53 | + > |
41 | 54 | </article> |
42 | 55 | <article> |
43 | | - <img src="git-branch.png" alt="Git branch illustration"/> |
| 56 | + <img src="git-branch.png" alt="Git branch illustration" /> |
44 | 57 | <h2>What is a BRANCH in Git?</h2> |
45 | 58 | <p class="intro"> |
46 | | - A branch in Git is an independent line of development — a lightweight pointer that lets you work on changes in isolation without affecting the main codebase. |
| 59 | + A branch in Git is an independent line of development — a lightweight |
| 60 | + pointer that lets you work on changes in isolation without affecting |
| 61 | + the main codebase. |
47 | 62 | </p> |
48 | 63 | <p class="content"> |
49 | | - Imagine a river that splits into a side channel. Work can proceed along the side channel independently; later, the two streams can be merged back together. In Git, this is exactly what a branch does: it diverges from a point in the commit history so |
| 64 | + Imagine a river that splits into a side channel. Work can proceed |
| 65 | + along the side channel independently; later, the two streams can be |
| 66 | + merged back together. In Git, this is exactly what a branch does: it |
| 67 | + diverges from a point in the commit history so |
50 | 68 | </p> |
51 | | - <a href="https://en.wikipedia.org/wiki/Branching_(version_control)" target="_blank" >Read more</a> |
| 69 | + <a |
| 70 | + href="https://en.wikipedia.org/wiki/Branching_(version_control)" |
| 71 | + target="_blank" |
| 72 | + >Read more</a |
| 73 | + > |
52 | 74 | </article> |
53 | 75 | </main> |
54 | 76 | <footer> |
55 | | - <p> |
56 | | - © Giorgi Natriashvili. All rights reserved. |
57 | | - </p> |
| 77 | + <p>© Giorgi Natriashvili. All rights reserved.</p> |
58 | 78 | </footer> |
59 | 79 | </body> |
60 | 80 | </html> |
0 commit comments