|
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> |
15 | | - </header> |
16 | | - <main> |
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. |
23 | | - </p> |
24 | | - <a href="">Read more</a> |
25 | | - </article> |
26 | | - </main> |
27 | | - <footer> |
28 | | - <p> |
29 | | - This is the default, provided code and no changes have been made yet. |
30 | | - </p> |
31 | | - </footer> |
| 11 | + <h1>Web Development Concepts</h1> |
| 12 | + <p>Understanding README files, Wireframes and Git Branches</p> |
| 13 | +</header> |
| 14 | + |
| 15 | +<main> |
| 16 | + <article> |
| 17 | + <img src="placeholder.svg" alt="README file illustration" /> |
| 18 | + |
| 19 | + |
| 20 | +<h2>What is a README File?</h2> |
| 21 | + |
| 22 | +<p> |
| 23 | + A README file explains a project. It usually contains information |
| 24 | + about the purpose of the project, installation instructions, |
| 25 | + usage examples and important notes for developers. |
| 26 | +</p> |
| 27 | + |
| 28 | +<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"> |
| 29 | + Read More |
| 30 | +</a> |
| 31 | + |
| 32 | + </article> |
| 33 | + |
| 34 | + <article> |
| 35 | + <img src="placeholder.svg" alt="Wireframe sketch" /> |
| 36 | + |
| 37 | +<h2>What is a Wireframe?</h2> |
| 38 | + |
| 39 | +<p> |
| 40 | + A wireframe is a visual plan of a webpage. It helps designers |
| 41 | + and developers organise content and layout before building |
| 42 | + the final website. |
| 43 | +</p> |
| 44 | + |
| 45 | +<a href="https://www.interaction-design.org/literature/topics/wireframing"> |
| 46 | + Read More |
| 47 | +</a> |
| 48 | + |
| 49 | + </article> |
| 50 | + |
| 51 | + <article> |
| 52 | + <img src="placeholder.svg" alt="Git branch workflow" /> |
| 53 | + |
| 54 | +<h2>What is a Git Branch?</h2> |
| 55 | + |
| 56 | +<p> |
| 57 | + A Git branch is an independent line of development. |
| 58 | + It allows developers to work on new features without |
| 59 | + affecting the main version of a project. |
| 60 | +</p> |
| 61 | + |
| 62 | +<a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell"> |
| 63 | + Read More |
| 64 | +</a> |
| 65 | + |
| 66 | + </article> |
| 67 | +</main> |
| 68 | + |
| 69 | +<footer> |
| 70 | + <p>Contact information and site details</p> |
| 71 | +</footer> |
| 72 | + |
32 | 73 | </body> |
33 | 74 | </html> |
0 commit comments