Skip to content

Commit ef20f27

Browse files
committed
Added background color to footer, that it shows above the context while being fixed
1 parent 2289b82 commit ef20f27

2 files changed

Lines changed: 46 additions & 21 deletions

File tree

Wireframe/index.html

Lines changed: 40 additions & 20 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,51 +10,71 @@
1010
<header>
1111
<h1>Code Hub</h1>
1212
<p>
13-
Learn to code with hands-on projects and expert guidance. Join our community of developers
13+
Learn to code with hands-on projects and expert guidance. Join our
14+
community of developers
1415
</p>
1516
</header>
1617
<main>
1718
<article>
18-
<img src="Readme.png" alt="README file illustration"/>
19+
<img src="Readme.png" alt="README file illustration" />
1920
<h2>What is a README file?</h2>
2021
<p class="intro">
21-
A README is the front door of any software project — the first document a visitor reads when they encounter your code.
22+
A README is the front door of any software project — the first
23+
document a visitor reads when they encounter your code.
2224
</p>
2325
<p class="content">
24-
Typically named README.md and written in Markdown, it lives at the root
25-
of a repository and renders automatically on platforms like GitHub. Its core
26-
purpose is to answer three questions immediately: what does this project do,
27-
how do I get it running, and how do I use it?<br>A well-crafted README...
26+
Typically named README.md and written in Markdown, it lives at the
27+
root of a repository and renders automatically on platforms like
28+
GitHub. Its core purpose is to answer three questions immediately:
29+
what does this project do, how do I get it running, and how do I use
30+
it?<br />A well-crafted README...
2831
</p>
29-
<a href="https://en.wikipedia.org/wiki/README" target="_blank">Read more</a>
32+
<a href="https://en.wikipedia.org/wiki/README" target="_blank"
33+
>Read more</a
34+
>
3035
</article>
3136
<article>
32-
<img src="Wireframe1.png" alt="Wireframe illustration"/>
37+
<img src="Wireframe1.png" alt="Wireframe illustration" />
3338
<h2>What is a WIREFRAME?</h2>
3439
<p class="intro">
35-
A wireframe is a skeletal blueprint of a digital interface — a low-fidelity sketch that maps out layout and structure before any visual design begins.
40+
A wireframe is a skeletal blueprint of a digital interface — a
41+
low-fidelity sketch that maps out layout and structure before any
42+
visual design begins.
3643
</p>
3744
<p class="content">
38-
Think of it as the floor plan of a building: it shows where the rooms are, how they connect, and how large each space is — but says nothing about paint colours or furniture. In UI/UX design, wireframes...
45+
Think of it as the floor plan of a building: it shows where the rooms
46+
are, how they connect, and how large each space is — but says nothing
47+
about paint colours or furniture. In UI/UX design, wireframes...
3948
</p>
40-
<a href="https://en.wikipedia.org/wiki/Website_wireframe" target="_blank">Read more</a>
49+
<a
50+
href="https://en.wikipedia.org/wiki/Website_wireframe"
51+
target="_blank"
52+
>Read more</a
53+
>
4154
</article>
4255
<article>
43-
<img src="git-branch.png" alt="Git branch illustration"/>
56+
<img src="git-branch.png" alt="Git branch illustration" />
4457
<h2>What is a BRANCH in Git?</h2>
4558
<p class="intro">
46-
A branch in Git is an independent line of development — a lightweight pointer that lets you work on changes in isolation without affecting the main codebase.
59+
A branch in Git is an independent line of development — a lightweight
60+
pointer that lets you work on changes in isolation without affecting
61+
the main codebase.
4762
</p>
4863
<p class="content">
49-
Imagine a river that splits into a side channel. Work can proceed along the side channel independently; later, the two streams can be merged back together. In Git, this is exactly what a branch does: it diverges from a point in the commit history so
64+
Imagine a river that splits into a side channel. Work can proceed
65+
along the side channel independently; later, the two streams can be
66+
merged back together. In Git, this is exactly what a branch does: it
67+
diverges from a point in the commit history so
5068
</p>
51-
<a href="https://en.wikipedia.org/wiki/Branching_(version_control)" target="_blank" >Read more</a>
69+
<a
70+
href="https://en.wikipedia.org/wiki/Branching_(version_control)"
71+
target="_blank"
72+
>Read more</a
73+
>
5274
</article>
5375
</main>
5476
<footer>
55-
<p>
56-
&copy; Giorgi Natriashvili. All rights reserved.
57-
</p>
77+
<p>&copy; Giorgi Natriashvili. All rights reserved.</p>
5878
</footer>
5979
</body>
6080
</html>

Wireframe/style.css

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ body {
2525
background: var(--paper);
2626
color: var(--ink);
2727
font: var(--font);
28+
height: 100%;
29+
margin: 0;
2830
}
2931
header {
3032
text-align: center;
@@ -47,14 +49,17 @@ https://www.w3.org/WAI/tutorials/page-structure/regions/
4749
main {
4850
max-width: var(--container);
4951
margin: 0 auto calc(var(--space) * 4) auto;
52+
flex: 1;
53+
padding-bottom: 100px;
5054
}
5155
footer {
5256
position: fixed;
5357
bottom: 0;
5458
left: 0;
5559
width: 100%;
5660
text-align: center;
57-
padding-bottom: var(--space);
61+
padding: 20px;
62+
background: var(--paper);
5863
}
5964
/* ====== Articles Grid Layout ====
6065
Setting the rules for how articles are placed in the main element.

0 commit comments

Comments
 (0)