Skip to content

Commit ef92e54

Browse files
mandipsangermandipsanger
committed
fix html errors
1 parent 3cd9c74 commit ef92e54

1 file changed

Lines changed: 84 additions & 40 deletions

File tree

‎Wireframe/index.html‎

Lines changed: 84 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
1-
<!DOCTYPE html>
2-
<html lang="en"User-agent: *
3-
Allow: />
1+
<!doctype html>
2+
<html lang="en">
43
<head>
54
<meta charset="UTF-8" />
65
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
@@ -9,40 +8,85 @@
98
</head>
109
<body>
1110
<header>
12-
<h1>Wireframe</h1>
13-
<p>
14-
Articles are a great way to share information and ideas with others. They can be used to educate, inform, or entertain readers on a wide range of topics. Whether you're writing about current events, technology, health, or any other subject, articles provide a platform for you to express your thoughts and insights. With the right research and writing skills, you can create engaging and informative articles that resonate with your audience and contribute to meaningful discussions. .These articles have beeen selected to explain the purpose of Read me file, Wireframe and Branch in Git.
15-
</p>
16-
</header>
17-
<main>
18-
<article>
19-
<img src="https://public-images.interaction-design.org/literature/articles/materials/ElementsofaWireframe.png" width="300" height="200" alt="Wireframe" />
20-
<h2>Purpose of Readme file</h2>
21-
<p>
22-
The purpose of a README file is to serve as the primary guide and quick-start manual for a project. Placed at the root of a folder or repository, it explains what the project does, how to install and use it, and how others can contribute.
23-
</p>
24-
<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a>
25-
</article>
26-
27-
<article>
28-
<img src="https://ubc-lib-geo.github.io/gis-workshop-waml-template/content/img/readme3.png" width="300" height="200" alt="Readme" />
29-
<h2>Purpose of Wireframe</h2>
30-
<p>
31-
A wireframe is a basic, two-dimensional visual representation of a web page, app interface, or product layout. You can think of it as a low-fidelity, functional sketch. Product designers and UX (user experience) professionals draw up wireframes to communicate how they plan to arrange and prioritize features, and how they intend for users to interact with its product or website.Wireframes typically depict only functionality, not the true style and visual elements of the final product. It's why most wireframes look simple: grayscale instead of colors, placeholders for images, and Lorem Ipsum for text.
32-
</p>
33-
<a href="https://www.productplan.com/glossary/wireframe">Read more</a>
34-
</article>
35-
36-
<article>
37-
<img src="https://framerusercontent.com/images/jmGsErVaXE9HMnmsIjHDba05DSg.png" width="300" height="200" alt="Branch" />
38-
<h2>Purpose of Branch</h2>
39-
<p>Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository. You always create a branch from an existing branch. Typically, you might create a new branch from the default branch of your repository.
40-
</p>
41-
<a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">Read more</a></article>
42-
</article>
43-
</main>
44-
</body>
45-
<footer>
46-
<p>Wifreframe project by Mandip Sanger </p>
47-
</footer>
48-
</html>
11+
<h1>Wireframe</h1>
12+
<p>
13+
Articles are a great way to share information and ideas with others.
14+
They can be used to educate, inform, or entertain readers on a wide
15+
range of topics. Whether you're writing about current events,
16+
technology, health, or any other subject, articles provide a platform
17+
for you to express your thoughts and insights. With the right research
18+
and writing skills, you can create engaging and informative articles
19+
that resonate with your audience and contribute to meaningful
20+
discussions. .These articles have beeen selected to explain the purpose
21+
of Read me file, Wireframe and Branch in Git.
22+
</p>
23+
</header>
24+
<main>
25+
<article>
26+
<img
27+
src="https://public-images.interaction-design.org/literature/articles/materials/ElementsofaWireframe.png"
28+
width="300"
29+
height="200"
30+
alt="Wireframe"
31+
/>
32+
<h2>Purpose of Readme file</h2>
33+
<p>
34+
The purpose of a README file is to serve as the primary guide and
35+
quick-start manual for a project. Placed at the root of a folder or
36+
repository, it explains what the project does, how to install and use
37+
it, and how others can contribute.
38+
</p>
39+
<a
40+
href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"
41+
>Read more</a
42+
>
43+
</article>
44+
45+
<article>
46+
<img
47+
src="https://ubc-lib-geo.github.io/gis-workshop-waml-template/content/img/readme3.png"
48+
width="300"
49+
height="200"
50+
alt="Readme"
51+
/>
52+
<h2>Purpose of Wireframe</h2>
53+
<p>
54+
A wireframe is a basic, two-dimensional visual representation of a web
55+
page, app interface, or product layout. You can think of it as a
56+
low-fidelity, functional sketch. Product designers and UX (user
57+
experience) professionals draw up wireframes to communicate how they
58+
plan to arrange and prioritize features, and how they intend for users
59+
to interact with its product or website.Wireframes typically depict
60+
only functionality, not the true style and visual elements of the
61+
final product. It's why most wireframes look simple: grayscale instead
62+
of colors, placeholders for images, and Lorem Ipsum for text.
63+
</p>
64+
<a href="https://www.productplan.com/glossary/wireframe">Read more</a>
65+
</article>
66+
67+
<article>
68+
<img
69+
src="https://framerusercontent.com/images/jmGsErVaXE9HMnmsIjHDba05DSg.png"
70+
width="300"
71+
height="200"
72+
alt="Branch"
73+
/>
74+
<h2>Purpose of Branch</h2>
75+
<p>
76+
Branches allow you to develop features, fix bugs, or safely experiment
77+
with new ideas in a contained area of your repository. You always
78+
create a branch from an existing branch. Typically, you might create a
79+
new branch from the default branch of your repository.
80+
</p>
81+
<a
82+
href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches"
83+
>Read more</a
84+
>
85+
</article>
86+
</main>
87+
88+
<footer>
89+
<p>Wifreframe project by Mandip Sanger</p>
90+
</footer>
91+
</body>
92+
</html>

0 commit comments

Comments
 (0)