Skip to content

Commit f9dbc7a

Browse files
fix google font links
1 parent 723c5df commit f9dbc7a

1 file changed

Lines changed: 40 additions & 29 deletions

File tree

Wireframe/index.html

Lines changed: 40 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,26 @@
11
<!DOCTYPE html>
22
<html lang="en">
3-
<head>
4-
<meta charset="UTF-8" />
5-
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
6-
<title>Wireframe</title>
7-
<link rel="stylesheet" href="style.css" />
8-
<link rel="preconnect" href="[fonts.googleapis.com](https://fonts.googleapis.com)">
9-
<link rel="preconnect" href="[fonts.gstatic.com](https://fonts.gstatic.com)" crossorigin>
10-
<link href="[fonts.googleapis.com](https://fonts.googleapis.com/css2?family=Kalam:wght@400;700&family=Inter:wght@400;600&display=swap)" rel="stylesheet">
11-
</head>
12-
<body>
13-
<header class="page-hero">
14-
<h1 class="page-hero">Wireframe</h1>
15-
<p class="page-subtitle">
16-
Learn about README files, wireframes, and Git branches.
17-
</p>
18-
</header>
19-
<main class="container">
3+
4+
<head>
5+
<meta charset="UTF-8" />
6+
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
7+
<title>Wireframe</title>
8+
<link rel="stylesheet" href="style.css" />
9+
<link rel="preconnect" href="https://fonts.googleapis.com">
10+
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
11+
12+
<link href="https://fonts.googleapis.com/css2?family=Kalam:wght@400;700&family=Inter:wght@400;600&display=swap"
13+
rel="stylesheet" />
14+
</head>
15+
16+
<body>
17+
<header class="page-hero">
18+
<h1 class="page-hero">Wireframe</h1>
19+
<p class="page-subtitle">
20+
Learn about README files, wireframes, and Git branches.
21+
</p>
22+
</header>
23+
<main class="container">
2024
<!-- Featured card (full width) -->
2125
<article class="card card--featured">
2226
<div class="card__media fake-img" aria-hidden="true">
@@ -26,7 +30,9 @@ <h1 class="page-hero">Wireframe</h1>
2630
<div class="card__body">
2731
<h2 class="card__title">What is the purpose of a README file?</h2>
2832
<p class="card__summary">
29-
A README introduces a project: what it is, why it exists, and how to use, install, run, and contribute to it. It orients new users and contributors, sets expectations (requirements, license, roadmap), and centralizes quick-start commands and links. In short, it’s the project’s front door and owner’s manual.
33+
A README introduces a project: what it is, why it exists, and how to use, install, run, and contribute to it.
34+
It orients new users and contributors, sets expectations (requirements, license, roadmap), and centralizes
35+
quick-start commands and links. In short, it’s the project’s front door and owner’s manual.
3036
</p>
3137
<a class="btn" href="#readme-details">Read More</a>
3238
</div>
@@ -42,7 +48,9 @@ <h2 class="card__title">What is the purpose of a README file?</h2>
4248
<div class="card__body">
4349
<h2 class="card__title">What is the purpose of a wireframe?</h2>
4450
<p class="card__summary">
45-
A wireframe is a low‑fidelity layout of a page. It maps structure, hierarchy, and placement of elements (headers, media, text, buttons) without visual polish. Teams use wireframes to align on content priority, user flow, and functionality early—reducing rework before design and code.
51+
A wireframe is a low‑fidelity layout of a page. It maps structure, hierarchy, and placement of elements
52+
(headers, media, text, buttons) without visual polish. Teams use wireframes to align on content priority,
53+
user flow, and functionality early—reducing rework before design and code.
4654
</p>
4755
<a class="btn" href="#wireframe-details">Read More</a>
4856
</div>
@@ -56,14 +64,16 @@ <h2 class="card__title">What is the purpose of a wireframe?</h2>
5664
<div class="card__body">
5765
<h2 class="card__title">What is a branch in Git?</h2>
5866
<p class="card__summary">
59-
A Git branch is an independent line of development. It lets you make changes, experiment, and review work without affecting the main history. When ready, merge the branch back (often via pull request) to integrate tested, reviewed changes into the primary codebase.
67+
A Git branch is an independent line of development. It lets you make changes, experiment, and review work
68+
without affecting the main history. When ready, merge the branch back (often via pull request) to integrate
69+
tested, reviewed changes into the primary codebase.
6070
</p>
6171
<a class="btn" href="#git-branch-details">Read More</a>
6272
</div>
6373
</article>
6474
</section>
6575

66-
<!-- “read more” anchors -->
76+
<!-- “read more” anchors -->
6777
<section class="details" id="readme-details" aria-label="README details">
6878
<h3>README essentials</h3>
6979
<ul>
@@ -95,11 +105,12 @@ <h3>Branch workflow highlights</h3>
95105
</ul>
96106
</section>
97107

98-
</main>
99-
<footer class="site-footer">
100-
<p >
101-
Liyema Mfengwana sprint 2 wireframe backlog.
102-
</p>
103-
</footer>
104-
</body>
105-
</html>
108+
</main>
109+
<footer class="site-footer">
110+
<p>
111+
Liyema Mfengwana sprint 2 wireframe backlog.
112+
</p>
113+
</footer>
114+
</body>
115+
116+
</html>

0 commit comments

Comments
 (0)