Skip to content

Commit 6c6749d

Browse files
d-odumosud-odumosu
committed
Deleted and recreated a new wireframe branch, i received a pr validation error due to creating the previous branch off another branch and not main
1 parent caa43a6 commit 6c6749d

1 file changed

Lines changed: 90 additions & 28 deletions

File tree

‎Wireframe/index.html‎

Lines changed: 90 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,95 @@
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-
</head>
9-
<body>
10-
<header>
11-
<h1>Wireframe</h1>
12-
<p>
13-
This is the default, provided code and no changes have been made yet.
14-
</p>
15-
</header>
3+
<head>
4+
<meta charset="UTF-8"/>
5+
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
6+
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
7+
<meta name="description"
8+
content="A beginner-friendly blog about README files, wireframes, and Git branches for learning web development."/>
9+
<title>The Blog | Learning Programming Basics</title>
10+
<link rel="preconnect" href="https://fonts.googleapis.com">
11+
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
12+
<link href="https://fonts.googleapis.com/css2?family=Bitcount+Grid+Single:wght@100..900&family=Cantarell:ital,wght@0,400;0,700;1,400;1,700&display=swap"
13+
rel="stylesheet">
14+
<link rel="stylesheet" href="style.css"/>
15+
</head>
16+
17+
<body>
18+
19+
<header class="site-header">
20+
21+
<div class="container header-content">
22+
23+
<div class="branding">
24+
<h1 class="site-title">The Blog</h1>
25+
<p class="site-tagline">A blog on learning programming</p>
26+
</div>
27+
28+
</div>
29+
30+
</header>
31+
32+
<div class="container">
1633
<main>
17-
<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>
25-
</article>
34+
<article class="article-feature">
35+
<img src="./images/md.png" alt="illustration of a readme.md file">
36+
<div class="article-feature-text">
37+
<h2>What is the purpose of a README file</h2>
38+
<p>
39+
according to GitHub Docs, a README file serves as the primary source of information about a project
40+
and
41+
helps users understand how to install, use, and contribute to it <em>(GitHub Docs, n.d.).</em>
42+
</p>
43+
<p>
44+
A README file is one of the most important documents within a software
45+
project. It is usually the first file that users, developers, recruiters,
46+
or potential employers look at when they visit a project's repository.
47+
The name "README" comes from the idea that it should be the file people
48+
read before doing anything else with the project.
49+
</p>
50+
<a class="article-read-more" href="#"
51+
aria-label="read more about what the purpose of a read me file does">README file ...</a>
52+
</div>
53+
</article>
54+
55+
<div class="article-secondary-flex">
56+
<article class="article-sec">
57+
<img src="./images/wireframes-01.png.webp" alt="illustration of a man showing a wireframe">
58+
<h2>What is the purpose of a wireframe</h2>
59+
<p>
60+
A wireframe is a simple visual representation of a website or application's layout. It acts as a
61+
blueprint.
62+
</p>
63+
<p>Figma describes a wireframe as a low-fidelity representation of a user interface that focuses on
64+
layout,
65+
structure, and functionality before visual design decisions are made <em>(Figma, n.d.).</em></p>
66+
<a class="article-read-more" href="#"
67+
aria-label="read more about the purpose of a wireframe">Wireframes</a>
68+
</article>
69+
70+
<article class="article-sec">
71+
<img src="./images/branch.webp" alt="illustration of a git tree branching out">
72+
<h2>What is a branch in Git?</h2>
73+
<p>Git documentation explains that branches allow developers to diverge from the main line of
74+
development
75+
and work independently on features before merging their changes back into the project
76+
<em>(Git SCM, n.d.).</em></p>
77+
<p>
78+
<p>
79+
A branch in Git is a separate line of development that allows developers to
80+
work on changes independently without affecting the main project.
81+
</p>
82+
<a class="article-read-more" href="#" aria-label="read more about branches on git">Git
83+
branching</a>
84+
</article>
85+
</div>
2686
</main>
27-
<footer>
28-
<p>
29-
This is the default, provided code and no changes have been made yet.
30-
</p>
31-
</footer>
32-
</body>
87+
</div>
88+
89+
<footer class="site-footer index-footer">
90+
<div class="container">
91+
<p>&copy; 2026 The Blog. All rights reserved.</p>
92+
</div>
93+
</footer>
94+
</body>
3395
</html>

0 commit comments

Comments
 (0)