|
1 | | -<!DOCTYPE html> |
| 1 | +<!doctype html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
|
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>Understanding Project Structure</h1> |
| 12 | + <p>A simple guide to README files, wireframes, and Git branches.</p> |
15 | 13 | </header> |
| 14 | + |
16 | 15 | <main> |
17 | 16 | <article> |
18 | | - <img src="placeholder.svg" alt="" /> |
19 | | - <h2>Title</h2> |
| 17 | + <img |
| 18 | + src="https://docs.github.com/assets/cb-55933/images/help/repository/readme-links.png" |
| 19 | + alt="readme file example" |
| 20 | + /> |
| 21 | + <h2>What is the purpose of a README file?</h2> |
| 22 | + <p> |
| 23 | + A README file is the foundational documentation for a software, |
| 24 | + dataset, or coding project. It serves as a project's "front door," |
| 25 | + designed to help users quickly understand what the project does, how |
| 26 | + to install and use it, and how to contribute. |
| 27 | + </p> |
| 28 | + <a |
| 29 | + href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes" |
| 30 | + >Read more</a |
| 31 | + > |
| 32 | + </article> |
| 33 | + |
| 34 | + <!-- Article 2: Wireframe --> |
| 35 | + <article> |
| 36 | + <img |
| 37 | + src="https://cdn-images.visual-paradigm.com/handbooks/agile-handbook/wireframe/02-newspaper-site-wireframe-example.png" |
| 38 | + alt="Wireframe sketch" |
| 39 | + /> |
| 40 | + <h2>What is the purpose of a wireframe?</h2> |
| 41 | + <p> |
| 42 | + The purpose of a wireframe is to act as a blueprint for a website or |
| 43 | + app. It provides a basic, stripped-down visual guide that outlines |
| 44 | + layout, structure, and functionality before any colors, images, or |
| 45 | + code are applied, ensuring everyone aligns on the project's |
| 46 | + foundation. |
| 47 | + </p> |
| 48 | + <a href="https://medium.com/design-bootcamp/wireframes-5d63f9d760a8" |
| 49 | + >Read more</a |
| 50 | + > |
| 51 | + </article> |
| 52 | + |
| 53 | + <!-- Article 3: Git branch --> |
| 54 | + <article> |
| 55 | + <img |
| 56 | + src="https://miro.medium.com/1*K9scAx1Ezd-KJFabaYseCw.jpeg" |
| 57 | + alt="Branch diagram" |
| 58 | + /> |
| 59 | + <h2>What is a branch in Git?</h2> |
20 | 60 | <p> |
21 | | - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, |
22 | | - voluptates. Quisquam, voluptates. |
| 61 | + A branch in Git is simply a lightweight movable pointer to one of |
| 62 | + these commits. The default branch name in Git is master . As you start |
| 63 | + making commits, you're given a master branch that points to the last |
| 64 | + commit you made. Every time you commit, the master branch pointer |
| 65 | + moves forward automatically. Note. |
23 | 66 | </p> |
24 | | - <a href="">Read more</a> |
| 67 | + <a href="https://www.w3schools.com/GIT/git_branch.asp?remote=github" |
| 68 | + >Read more</a |
| 69 | + > |
25 | 70 | </article> |
26 | 71 | </main> |
27 | 72 | <footer> |
|
0 commit comments