|
1 | | -<!DOCTYPE html> |
| 1 | +<!doctype html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8" /> |
|
9 | 9 | <body> |
10 | 10 | <header> |
11 | 11 | <h1>Understanding README Files, Wireframes and Git Branches</h1> |
12 | | - <p> |
13 | | - A simple guide explaining three important web development concepts.</p> |
| 12 | + <p>A simple guide explaining three important web development concepts.</p> |
14 | 13 | </header> |
15 | 14 | <main> |
16 | 15 | <!--Top article (full-width)--> |
17 | 16 | <article class="top-article" id="readme-article"> |
18 | 17 | <img src="placeholder.svg" alt="Illustration of a README file" /> |
19 | 18 | <h2>What is the purpose of a README file?</h2> |
20 | 19 | <p> |
21 | | - A README file explains what a project is about, how to use it, and any important information someone needs before working with the project code. |
| 20 | + A README file explains what a project is about, how to use it, and any |
| 21 | + important information someone needs before working with the project |
| 22 | + code. |
22 | 23 | </p> |
23 | 24 | <a href="https://www.makeareadme.com/" target="_blank">Read more</a> |
24 | 25 | </article> |
25 | 26 |
|
26 | 27 | <!--Bottom two articles side -by-side--> |
27 | 28 |
|
28 | | - <section class="bottom-articles"> |
29 | | - |
30 | | - <article id="wireframe-article"> |
31 | | - <img src="placeholder.svg" alt="Example of a webpage wireframe"/> |
32 | | - <h2>What is the purpose of a wireframe?</h2> |
33 | | - <p> |
34 | | - A wireframe is a simple layout plan that shows where content will go on a webpage before you start designing or coding. |
35 | | - </p> |
36 | | - |
37 | | - <a href="https://careerfoundry.com/en/blog/ux-design/what-is-a-wireframe/" target="_blank">Read more</a> |
38 | | - </article> |
39 | | - |
40 | | - <article id="branch-article"> |
41 | | - <img src="placeholder.svg" alt="Diagram showing Git branches"/> |
42 | | - <h2>What is a branch in Git?</h2> |
43 | | - <p> |
44 | | - A Git baranch lets developers work on new features without affecting the main project. When finished, the branch can be merged back in. |
45 | | - </p> |
46 | | - <a href="https://www.atlassian.com/git/tutorials/using-branches" target="_blank">Read more</a> |
47 | | - </article> |
| 29 | + <section class="bottom-articles"> |
| 30 | + <article id="wireframe-article"> |
| 31 | + <img src="placeholder.svg" alt="Example of a webpage wireframe" /> |
| 32 | + <h2>What is the purpose of a wireframe?</h2> |
| 33 | + <p> |
| 34 | + A wireframe is a simple layout plan that shows where content will go |
| 35 | + on a webpage before you start designing or coding. |
| 36 | + </p> |
48 | 37 |
|
49 | | - </section> |
| 38 | + <a |
| 39 | + href="https://careerfoundry.com/en/blog/ux-design/what-is-a-wireframe-guide/" |
| 40 | + target="_blank" |
| 41 | + >Read more</a |
| 42 | + > |
| 43 | + </article> |
50 | 44 |
|
| 45 | + <article id="branch-article"> |
| 46 | + <img src="placeholder.svg" alt="Diagram showing Git branches" /> |
| 47 | + <h2>What is a branch in Git?</h2> |
| 48 | + <p> |
| 49 | + A Git baranch lets developers work on new features without affecting |
| 50 | + the main project. When finished, the branch can be merged back in. |
| 51 | + </p> |
| 52 | + <a |
| 53 | + href="https://www.atlassian.com/git/tutorials/using-branches" |
| 54 | + target="_blank" |
| 55 | + >Read more</a |
| 56 | + > |
| 57 | + </article> |
| 58 | + </section> |
51 | 59 | </main> |
52 | 60 | <footer> |
53 | 61 | <p> |
54 | | - Footers usually contain contact links and other information about the site overall |
| 62 | + Footers usually contain contact links and other information about the |
| 63 | + site overall |
55 | 64 | </p> |
56 | | - |
57 | 65 | </footer> |
58 | 66 | </body> |
59 | 67 | </html> |
0 commit comments