Skip to content

Commit 468038b

Browse files
mandipsangermandipsanger
committed
wireframe
1 parent 6ab0464 commit 468038b

1 file changed

Lines changed: 69 additions & 10 deletions

File tree

‎Wireframe/index.html‎

Lines changed: 69 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!DOCTYPE html>
1+
<!doctype html>
22
<html lang="en">
33
<head>
44
<meta charset="UTF-8" />
@@ -10,24 +10,83 @@
1010
<header>
1111
<h1>Wireframe</h1>
1212
<p>
13-
This is the default, provided code and no changes have been made yet.
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.
1422
</p>
1523
</header>
1624
<main>
1725
<article>
18-
<img src="placeholder.svg" alt="" />
19-
<h2>Title</h2>
26+
<img
27+
src="https://public-images.interaction-design.org/literature/articles/materials/ElementsofaWireframe.png"
28+
width="300"
29+
height="200"
30+
alt="Wireframe Design"
31+
/>
32+
<h2>Purpose of Readme file</h2>
2033
<p>
21-
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
22-
voluptates. Quisquam, voluptates.
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.
2338
</p>
24-
<a href="">Read more</a>
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 file example"
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="Git Branch Visual Graph"
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+
>
2585
</article>
2686
</main>
87+
2788
<footer>
28-
<p>
29-
This is the default, provided code and no changes have been made yet.
30-
</p>
89+
<p>Wifreframe project by Mandip Sanger</p>
3190
</footer>
3291
</body>
3392
</html>

0 commit comments

Comments
 (0)