Skip to content

London | 26-MAY-ITP | Yonatan Teklemariam | Sprint 2 | Feature/wireframe #1340

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

Open
Yonatanteklemariam wants to merge 2 commits into
base: main
Choose a base branch
from
+262 −110
Open

London | 26-MAY-ITP | Yonatan Teklemariam | Sprint 2 | Feature/wireframe #1340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce36dda
Resolve merge conflict in style.css
Yonatanteklemariam May 22, 2026
aad4ec4
Resolve merge conflict in index.html
Yonatanteklemariam May 22, 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
126 changes: 95 additions & 31 deletions Wireframe/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,33 +1,97 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Wireframe</title>
<link rel="stylesheet" href="style.css" />
</head>
<body>
<header>
<h1>Wireframe</h1>
<p>
This is the default, provided code and no changes have been made yet.
</p>
</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>
<a href="">Read more</a>
</article>
</main>
<footer>
<p>
This is the default, provided code and no changes have been made yet.
</p>
</footer>
</body>
</html>

<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>My Wireframe Design</title>
<link rel="stylesheet" href="style.css">
</head>

<body>

<!-- header -->
<header class="page-header">
<h1>Basics of Web Development Designs</h1>
<p>README files, wireframes, and Git branches explained clearly</p>
</header>

<!-- Hero Image Placeholder -->
<div class="hero">
<img
src="https://thf.bing.com/th/id/OIP.YsDV0VqSm_xNM6gRZ8N9UgHaEK?w=271&h=180&c=7&r=0&o=7&cb=thfc1falcon&dpr=1.3&pid=1.7&rm=3"
alt="readme diagram" class="placeholder">
</div>

<!-- Main Article -->
<main class="main-article">
<h2>What is the purpose of a README file?</h2>
<p>A <strong>README</strong> file explains what a project is, how it works, and how to use it. It usually includes
installation
steps, usage instructions, and important notes. The purpose is to help anyone understand the project quickly
without reading the entire codebase.
A README.md is an important document in a repository that introduces the project and explains its purpose, setup,
and usage to help users and developers understand and contribute to it.
Uses Markdown (.md) for formatted documentation and is usually the first file users read in a project.
Provides a project overview, installation instructions, configuration details, and usage examples such as code or
command-line commands.
May include license information, contributor credits, and appears well-formatted on platforms like GitHub.
A README file is meant to act as the front door to a project, giving anyone who encounters it a clear and
immediate understanding of what the project is about and how to interact with it. It explains the project’s
purpose, its goals, and the problems it aims to solve, while also guiding users through installation, usage, and
any important requirements. A strong README also helps future contributors by documenting decisions, structure,
and expectations, making collaboration smoother and reducing confusion. It becomes a reference point that keeps
the project understandable even months or years later, ensuring that the work remains accessible not only to
others but also to the original creator when returning after a long break.
</p>
<br><br>
<a href="https://www.bing.com/ck/a?!&&p=0e549038c9976fa751249f6e377372e242f89736085ed98c81c4f553d43b47c5JmltdHM9MTc3OTMyMTYwMA&ptn=3&ver=2&hsh=4&fclid=208fb4e6-66f9-61be-37f1-a3e567b76078&psq=readme+file+meaning&u=a1aHR0cHM6Ly93d3cuZ2Vla3Nmb3JnZWVrcy5vcmcvZ2l0L3doYXQtaXMtcmVhZG1lLW1kLWZpbGUv"
aria-label="Read more about readme files" class="btn">Read More</a>
</main>

<!-- Small Articles Section -->
<div class="small-articles">

<article class="small-article">
<img
src="https://thf.bing.com/th/id/OIP.tW2YTG0Gl_HHGRa0SvM8hwHaFj?w=191&h=180&c=7&r=0&o=7&cb=thfc1falcon&dpr=1.3&pid=1.7&rm=3"
alt="wireframe diagram" class="placeholder-small">
<h3>What is the purpose of a wireframe?</h3>
<p>A <strong>wireframe</strong> is a simple visual layout that shows the structure of a webpage before design or
coding begins. It
helps developers and designers plan where elements should go and how the page should flow.</p>
<a href="https://www.bing.com/ck/a?!&&p=b7ce4e20dfeb568901a83af5b4240b863c21d97b8e784467aa170932e2aba9b1JmltdHM9MTc3OTMyMTYwMA&ptn=3&ver=2&hsh=4&fclid=208fb4e6-66f9-61be-37f1-a3e567b76078&psq=wireframe+meaning&u=a1aHR0cHM6Ly93d3cuZ2Vla3Nmb3JnZWVrcy5vcmcvYmxvZ3Mvd2hhdC1pcy13aXJlZnJhbWluZy8"
aria-label="Read more about wireframes" class="btn">Read More</a>
</article>


<article class="small-article">
<img
src="https://thf.bing.com/th/id/OIP.e8ErcddqmrslMLMzf3tLUgHaEK?w=333&h=187&c=7&r=0&o=7&cb=thfc1falcon&dpr=1.3&pid=1.7&rm=3"
alt="git branching diagram" class="placeholder-small">
<h3>What is a branch in Git?</h3>
<p>A <strong>Git branch</strong> is a separate version of your project where you can work on new features without
affecting the
main code. Branches allow safe experimentation and make collaboration easier. Therefore.</p>
<a href="https://www.bing.com/ck/a?!&&p=a3106f4d918b1bd91968281781229db63f035c1379f56a2aaa6ebbb47092becfJmltdHM9MTc3OTMyMTYwMA&ptn=3&ver=2&hsh=4&fclid=208fb4e6-66f9-61be-37f1-a3e567b76078&psq=git+branching+means&u=a1aHR0cHM6Ly93d3cuZ2Vla3Nmb3JnZWVrcy5vcmcvZ2l0L2ludHJvZHVjdGlvbi10by1naXQtYnJhbmNoLw"
aria-label="Read more about Git branching" class="btn">Read More</a>
</article>

</div>
</main>
<!-- footer -->
<footer>
<div class="footer-note">
<p>For more information, please contact us at: Email: <a href="mailto:info@mywireframedesign.com"
target="_blank">jante26uk@gmail.com</a></p>
<p>Telephone: <a href="tel:+1234567890" target="_blank">07350989507</a></p>
<p>Address: <a
href="https://www.google.com/maps/place/29+fauna+field,+dunstable/@51.8892291,-0.5159181,3a,75y,233.86h,90t/data=!3m4!1e1!3m2!1smLOk3gqmcMjC07E1hbElkg!2e0!4m2!3m1!1s0x48764f036c42a891:0xae3cf387fd9cf1dd?sa=X&ved=1t:3780&ictx=111"
target="_blank">29
Fauna Field, Dusntable, UK</a></p><br>
</div>
<p>&copy; 2026 My Wireframe Design. All rights reserved.</p>
</footer>
</body>

</html>
246 changes: 167 additions & 79 deletions Wireframe/style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,89 +1,177 @@
/* Here are some starter styles
You can edit these or replace them entirely
It's showing you a common way to organise CSS
And includes solutions to common problems
As well as useful links to learn more */

/* ====== Design Palette ======
This is our "design palette".
It sets out the colours, fonts, styles etc to be used in this design
At work, a designer will give these to you based on the corporate brand, but while you are learning
You can design it yourself if you like
Inspect the starter design with Devtools
Click on the colour swatches to see what is happening
I've put some useful CSS you won't have learned yet
For you to explore and play with if you are interested
https://web.dev/articles/min-max-clamp
https://scrimba.com/learn-css-variables-c026
====== Design Palette ====== */
:root {
--paper: oklch(7 0 0);
--ink: color-mix(in oklab, var(--color) 5%, black);
--font: 100%/1.5 system-ui;
--space: clamp(6px, 6px + 2vw, 15px);
--line: 1px solid;
--container: 1280px;
}
/* ====== Base Elements ======
General rules for basic HTML elements in any context */
* {
margin: 0;
padding: 0;
box-sizing: border-box;
font-family: 'Arial', sans-serif;
}

html,
body {
height: 100%;
}

body {
background: var(--paper);
color: var(--ink);
font: var(--font);
background-color: #3c3f72;
color: #080000;
font-family: 'Arial', sans-serif;
line-height: 1.5;
font-size: 1em;
display: flex;
flex-direction: column;
}

.page-header {
background-color: #d0bee3;
color: #1a082c;
text-align: center;
text-shadow: 2px 2px 4px rgba(225, 226, 237, 0.982);
margin-bottom: 40px;
padding: 30px;
font-size: 1.5em;
}
a {
padding: var(--space);
border: var(--line);
max-width: fit-content;

.page-header h1 {
font-size: 2em;
margin-bottom: 5px;
}
img,
svg {

.hero .placeholder {
width: 100%;
object-fit: cover;
height: 600px;
background-color: #d0bee3;
border: 2px dashed #1a082c;
border-radius: 10px;
margin-bottom: 20px;

}

.hero {
margin-right: 20px;
margin-left: 20px;
}

.main-article {
flex: 1;
background: white;
padding-top: 45px;
padding-left: 15px;
padding-right: 15px;
padding-bottom: 15px;
border: 2px solid #000;
border-radius: 10px;
margin-bottom: 20px;
text-align: justify;
margin-right: 20px;
margin-left: 20px;

}

.main-article p,
.small-article p {
font-size: 1.2em;
}
/* ====== Site Layout ======
Setting the overall rules for page regions
https://www.w3.org/WAI/tutorials/page-structure/regions/
*/
main {
max-width: var(--container);
margin: 0 auto calc(var(--space) * 4) auto;


.small-article h3 {
font-size: 1em;
color: #350763;
margin-bottom: 15px;
text-shadow: 2px 2px 4px rgba(225, 226, 237, 0.982);
}


.main-article h2 {
color: #350763;
margin-bottom: 15px;
text-shadow: 2px 2px 4px rgba(225, 226, 237, 0.982);
}

.btn {
display: inline-block;
padding: 4px 14px;
background-color: #350763;
color: white;
text-decoration: none;
border-radius: 5px;
margin-top: 10px;
font-size: 1.2em;
font-weight: bold;
}

.btn:hover {
background-color: #c3e7fb;
color: #1a082c;
}

.small-articles {
display: flex;
gap: 20px;
margin-bottom: 20px;
margin-right: 20px;
margin-left: 20px;
text-align: justify;


}

.small-article {
flex: 1;
background: white;
padding: 15px;
border: 2px solid #000;
border-radius: 10px;
}

.small-article h3 {
color: #350763;
margin-bottom: 10px;
font-size: 1.2em;
}

.placeholder-small {
width: 100%;
height: 450px;
background-color: #d0bee3;
border: 2px dashed #1a082c;
border-radius: 10px;
margin-bottom: 15px;
}

footer {
position: fixed;
bottom: 0;
background-color: #d0bee3;
color: #1a082c;
text-align: center;
text-shadow: 2px 2px 4px rgba(225, 226, 237, 0.982);
padding: 10px 15px;
line-height: 1.3;
font-size: 1em;
margin-top: auto;

}
/* ====== 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
Play with the options that come up.
https://developer.chrome.com/docs/devtools/css/grid
https://gridbyexample.com/learn/
*/
main {
display: grid;
grid-template-columns: 1fr 1fr;
gap: var(--space);
> *:first-child {
grid-column: span 2;
}
}
/* ====== Article Layout ======
Setting the rules for how elements are placed in the article.
Now laying out just the INSIDE of the repeated card/article design.
Keeping things orderly and separate is the key to good, simple CSS.
*/
article {
border: var(--line);
padding-bottom: var(--space);
text-align: left;
display: grid;
grid-template-columns: var(--space) 1fr var(--space);
> * {
grid-column: 2/3;
}
> img {
grid-column: span 3;
}

footer p {
font-weight: bold;
}

.footer-note {
font-size: 22px;
color: #1a082c;
margin-bottom: 5px;
text-shadow: 2px 2px 4px rgba(210, 213, 244, 0.982);
padding-top: 10px;
padding-bottom: 10px;
padding-left: 15px;
padding-right: 15px;
border-bottom: none;
<<<<<<< HEAD
/* optional: remove the thick bar */
=======>>>>>>>59daf8a (Updated wireframe HTML and CSS) border-radius: 10px;


}

.footer-note a:hover {
color: #c6e9e9;
text-shadow: 2px 2px 4px rgba(25, 32, 112, 0.982);

}
Loading