|
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
5 | 5 | <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
6 | | - <title>Golden Travel</title> |
| 6 | + <title>Software development UNI</title> |
7 | 7 | <link rel="stylesheet" href="style.css" /> |
8 | 8 | </head> |
9 | 9 | <body> |
10 | 10 | <header> |
11 | | - <h1>Checking push to GitHub</h1> |
| 11 | + <h1>Code Hub</h1> |
12 | 12 | <p> |
13 | | - We create unforgettable travel experiences for our customers. We deliver your dream vacation! |
| 13 | + Learn to code with hands-on projects and expert guidance. Join our community of developers |
14 | 14 | </p> |
15 | 15 | </header> |
16 | 16 | <main> |
17 | 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 | + <img src="Readme.png" alt="README file illustration" id="readmeImg"/> |
| 19 | + <h2>What is a README file?</h2> |
| 20 | + <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 | + </p> |
| 23 | + <p class="content"> |
| 24 | + Typically named README.md and written in Markdown, it lives at the root of a repository and renders automatically on platforms like GitHub. Its core purpose is to answer three questions immediately: what does this project do, how do I get it running, and how do I use it?<br>A well-crafted README... |
| 25 | + </p> |
| 26 | + <a href="">Read more</a> |
| 27 | + </article> |
| 28 | + <article> |
| 29 | + <img src="Wireframe1.png" alt="Wireframe illustration" id="readmeImg"/> |
| 30 | + <h2>What is a WIREFRAME?</h2> |
| 31 | + <p class="intro"> |
| 32 | + 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. |
| 33 | + </p> |
| 34 | + <p class="content"> |
| 35 | + 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... |
| 36 | + </p> |
| 37 | + <a href="">Read more</a> |
| 38 | + </article> |
| 39 | + <article> |
| 40 | + <img src="git-branch.png" alt="Git branch illustration" id="readmeImg"/> |
| 41 | + <h2>What is a BRANCH in Git?</h2> |
| 42 | + <p class="intro"> |
| 43 | + 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. |
| 44 | + </p> |
| 45 | + <p class="content"> |
| 46 | + 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 |
23 | 47 | </p> |
24 | 48 | <a href="">Read more</a> |
25 | 49 | </article> |
|
0 commit comments