Skip to content

West Midlands | Jan-2026 | Arunkumar Akilan | Sprint 1 | Wireframe to Web Code #995

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
arunkumarakilan wants to merge 8 commits into from
Closed

West Midlands | Jan-2026 | Arunkumar Akilan | Sprint 1 | Wireframe to Web Code #995

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
d2d8387
Update header title and description
Jan 20, 2026
b64dc63
Add and style footer navigation
Jan 20, 2026
b5bc4d1
Add wireframe, README, and Git branch articles
Jan 20, 2026
32d8416
style: layout articles using CSS grid
Jan 20, 2026
f1416d5
Add footer with nav and contact details
Jan 20, 2026
27b3408
Format header description paragraph for readability
Jan 27, 2026
b2681d2
Improve footer indentation
Jan 27, 2026
0cbf4b1
Center page header and improve article spacing
Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 38 additions & 13 deletions Wireframe/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,26 +8,51 @@
</head>
<body>
<header>
<h1>Wireframe</h1>
<h1>Understanding Git and Wireframes</h1>
<p>
This is the default, provided code and no changes have been made yet.
This page explains the basics of Git, the purpose of a README file, and how wireframes help developers plan and structure a webpage before writing code. It gives a clear overview of how these tools are used together in real-world web development.
</p>
Comment thread
arunkumarakilan marked this conversation as resolved.
Outdated
</header>
<main>
<article>
<img src="placeholder.svg" alt="" />
<h2>Title</h2>
<p>
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
voluptates. Quisquam, voluptates.
</p>
<section>
<article class="card">
<img src="placeholder.svg" alt="Wireframe illustration" />
<div class="card-content">
<h2>Purpose of a Wireframe</h2>
<p> A wireframe is a simple visual guide used to plan layout and structure
before adding design and content.</p>
<a href="">Read more</a>
</div>
</article>
<article class="card">
<img src="placeholder.svg" alt="Git illustration" />
<div class="card-content">
<h2>Purpose of a README File</h2>
<p>A README file explains what a project is about, how to set it up, and how to use it. It helps other developers understand the project quickly without reading all the code.</p>
<a href="">Read more</a>
</div>
</article>
<article class="card">
<img src="placeholder.svg" alt="Git illustration" />
<div class="card-content">
<h2>What is a Git Branch</h2>
<p>A Git branch is a separate version of the code that allows developers to work on new features or fixes without affecting the main codebase. Once the work is complete, the branch can be merged back into the main branch safely.</p>
<a href="">Read more</a>
</div>
</article>
</section>

</main>
<footer>
<p>
This is the default, provided code and no changes have been made yet.
</p>
</footer>
<nav>
<a href="#">Home</a>
<a href="#">About</a>
<a href="mailto:arunnkumar7@gmail.com">Contact</a>
<a href="https://github.com/arunkumarakilan" target="_blank" rel="noopener">GitHub</a>
<a href="https://www.linkedin.com/in/arunkumar-akilan-0a87aa3a1/" target="_blank" rel="noopener">LinkedIn</a>
</nav>
<p>© 2026 Arunkumar Akilan</p>

</footer>
</body>
Comment thread
arunkumarakilan marked this conversation as resolved.
Outdated
</html>
31 changes: 31 additions & 0 deletions Wireframe/style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ body {
background: var(--paper);
color: var(--ink);
font: var(--font);
padding: 80px;
}
a {
padding: var(--space);
Expand All @@ -48,12 +49,34 @@ https://www.w3.org/WAI/tutorials/page-structure/regions/
main {
max-width: var(--container);
margin: 0 auto calc(var(--space) * 4) auto;
padding-bottom: 80px;
}
Copy link
Copy Markdown
Contributor

@cjyuan cjyuan Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two main selectors (lines 57 and 95). It is better to merge them into one. (I know you didn't write them, but that's one possible improvement you can easily do).

There are also a few selectors that are related to main (lines 121-128). It is better to place all the selectors related to main element together.

footer {
position: fixed;
left: 0;
right: 0;
bottom: 0;
z-index: 10;
padding: 4px 0;
background: white;
text-align: center;
}
footer nav{
display: flex;
justify-content: center;
align-items: center;
gap: var(--space);
flex-direction: row;
flex-wrap: wrap;
}
footer nav a{
padding: 4px 8px;
border: none;
max-width: fit-content;
text-decoration: none;
color: #222;
font-size: 0.9rem;
}
/* ====== Articles Grid Layout ====
Setting the rules for how articles are placed in the main element.
Inspect this in Devtools and click the "grid" button in the Elements view
Expand Down Expand Up @@ -87,3 +110,11 @@ article {
grid-column: span 3;
}
}
main>section{
display:grid;
grid-template-columns: 1fr 1fr;
gap: 16px;
}
main>section article:first-child {
grid-column: 1 / -1;
}
Loading