Skip to content

Commit 3f7b510

Browse files
committed
creating the page based on the wireframe
1 parent 55de4e4 commit 3f7b510

2 files changed

Lines changed: 55 additions & 11 deletions

File tree

Wireframe/index.html

Lines changed: 41 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -10,24 +10,54 @@
1010
<header>
1111
<h1>Wireframe</h1>
1212
<p>
13-
This is the default, provided code and no changes have been made yet.
13+
Wireframe is low-fidelity, Visual Blueprint of a webpage or app interface.
1414
</p>
1515
</header>
16+
1617
<main>
18+
<!-- what is the purpose of README article -->
1719
<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>
20+
<img src="https://www.makeareadme.com/images/open-graph-logo.png?v=20181203" alt="README image" />
21+
<h2>README file</h2>
22+
23+
<details> <summary>The purpose of README file is to give information about the project and how to use it
24+
</summary>
25+
<p> A README file is the "front door" of your project. it is typically a text file (usuallyREADME.md using Markdown) located in the root directory of your code</p>
26+
</details>
27+
<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a>
2528
</article>
29+
30+
<!--purpose of wireframe article-->
31+
<article>
32+
<img src="https://github.com/Dagim-Daniel/Module-Onboarding/blob/main/Wireframe/wireframe.png?raw=true" alt="">
33+
<h2>Purpose of Wireframe</h2>
34+
<details>
35+
<summary>
36+
It establish the basic Structure of a page.
37+
</summary>
38+
<p>Wireframing is the perfect way for the designers to gauge how the user would interact with the interface. Before adding visual considerations like color or images, they serve as an outline to get the team on the same page early.</p>
39+
</details>
40+
<a href="https://medium.com/design-bootcamp/wireframes-5d63f9d760a8">Read more</a>
41+
</article>
42+
43+
<!-- what is branch git article -->
44+
<article>
45+
<img src="https://cdn.iconscout.com/icon/free/png-256/free-git-branch-logo-icon-svg-download-png-1982843.png" alt="">
46+
<h2>Branch in Git</h2>
47+
<details>
48+
<summary>
49+
In Git, branch a pointer to a snapshot of your changes.
50+
</summary>
51+
52+
<p>Branch is like a separate working copy of your project in Git. It allows you to make changes without affecting the main branch (often called "main" or "master").</p>
53+
</details>
54+
<a href="https://www.w3schools.com/git/git_branch.asp">Read more</a>
55+
</article>
56+
2657
</main>
58+
2759
<footer>
28-
<p>
29-
This is the default, provided code and no changes have been made yet.
30-
</p>
60+
<p>Author: Dagim Daniel : <a href= "mailto:dagimdan19@gmail.com">dagimdan19@gmail.com</a></p>
3161
</footer>
3262
</body>
3363
</html>

Wireframe/style.css

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,14 @@ a {
3636
border: var(--line);
3737
max-width: fit-content;
3838
}
39+
footer a
40+
{
41+
padding: var(--space);
42+
border: none;
43+
text-align: center;
44+
max-width: fit-content;
45+
46+
}
3947
img,
4048
svg {
4149
width: 100%;
@@ -45,6 +53,10 @@ svg {
4553
Setting the overall rules for page regions
4654
https://www.w3.org/WAI/tutorials/page-structure/regions/
4755
*/
56+
header {
57+
text-align: center;
58+
padding: var(--space);
59+
}
4860
main {
4961
max-width: var(--container);
5062
margin: 0 auto calc(var(--space) * 4) auto;
@@ -53,6 +65,8 @@ footer {
5365
position: fixed;
5466
bottom: 0;
5567
text-align: center;
68+
background-color: blanchedalmond;
69+
width:100%;
5670
}
5771
/* ====== Articles Grid Layout ====
5872
Setting the rules for how articles are placed in the main element.

0 commit comments

Comments
 (0)