|
| 1 | +<!doctype html> |
| 2 | +<html lang="en"> |
| 3 | + <head> |
| 4 | + <meta charset="UTF-8" /> |
| 5 | + <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
| 6 | + <title>README, Wireframes and Git Branches</title> |
| 7 | + <link rel="stylesheet" href="style.css" /> |
| 8 | + </head> |
| 9 | + <body> |
| 10 | + <header> |
| 11 | + <h1>README, Wireframes and Git Branches</h1> |
| 12 | + <p>A simple guide to three important web development concepts.</p> |
| 13 | + </header> |
| 14 | + <main> |
| 15 | + <article> |
| 16 | + <img |
| 17 | + src="https://myscope.training/images/RDM-module/figure_22.jpg" |
| 18 | + alt="README file illustration" |
| 19 | + /> |
| 20 | + <h2>What is the purpose of a README file?</h2> |
| 21 | + <p> |
| 22 | + A README file explains what a project is, how it works, and how |
| 23 | + someone can use it. It often includes setup instructions, features, |
| 24 | + and important notes for developers. |
| 25 | + </p> |
| 26 | + <a |
| 27 | + href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes" |
| 28 | + >Read more</a |
| 29 | + > |
| 30 | + </article> |
| 31 | + |
| 32 | + <article> |
| 33 | + <img |
| 34 | + src="https://www.oursky.com/images/blogs/86256bf2c9_6799482b54769870a1e9c883_1.jpeg" |
| 35 | + alt="Wireframe file illustration" |
| 36 | + /> |
| 37 | + <h2>What is the purpose of a wireframe?</h2> |
| 38 | + <p> |
| 39 | + A wireframe is a simple plan for a webpage or app. It shows where |
| 40 | + content, images, buttons, and sections will go before the final design |
| 41 | + is created. |
| 42 | + </p> |
| 43 | + <a |
| 44 | + href="https://github.com/dwyl/learn-wireframing/blob/master/README.md" |
| 45 | + >Read more</a |
| 46 | + > |
| 47 | + </article> |
| 48 | + |
| 49 | + <article> |
| 50 | + <img |
| 51 | + src="https://www.sqlshack.com/wp-content/uploads/2020/09/git-branch-and-timelines.png" |
| 52 | + alt="Git branch file illustration" |
| 53 | + /> |
| 54 | + <h2>What is a branch in Git?</h2> |
| 55 | + <p> |
| 56 | + A branch in Git is a separate version of a project. It lets developers |
| 57 | + work on new features or fixes without changing the main version of the |
| 58 | + code. |
| 59 | + </p> |
| 60 | + <a |
| 61 | + href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches" |
| 62 | + >Read more</a |
| 63 | + > |
| 64 | + </article> |
| 65 | + </main> |
| 66 | + <footer> |
| 67 | + <p>Created as a beginner guide to key web development terms.</p> |
| 68 | + </footer> |
| 69 | + </body> |
| 70 | +</html> |
0 commit comments