Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
112 changes: 82 additions & 30 deletions Wireframe/index.html
Original file line number Diff line number Diff line change
@@ -1,33 +1,85 @@
<!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>
Copy link
Contributor

Choose a reason for hiding this comment

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

According to the wireframe exercise, each article should have a 'Read more' link (styled as a button) that will bring the user to an article about that topic. Can you add this back?

Copy link
Author

Choose a reason for hiding this comment

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

Done ✅


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



</head>

<body>
<header>
<h1>Wireframe to Web Code|Coursework</h1>
<p>
This page provides an overview of the purpose of the README file and the wireframe, as well as the meaning of the
"branch" in Git
</p>
</header>
<main>
<article class="article full">
<div class="image-placeholder">
<img src="https://bookface-images.s3.amazonaws.com/logos/3e5eb5fb62a7ee0260f47285d1343af2fd07b721.png"
alt="Image for README" width="400" height="200">
</div>
<div class="article-content">
<h2>README file</h2>
<p>A README is a text file that introduces and explains a project. It contains information that is commonly
required to understand what the project is about.<br>A good README helps others understand your project
quickly. It usually includes installation steps, usage examples, license info, and how to contribute. It's an
easy way to answer questions that your audience will likely have regarding how to install and use your project
and also how to collaborate with you.</p>
</div>
<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"
class="read-more">Read more</a>
</article>
<div class="articles-row">
<article class="article half">
<div class="image-placeholder">
<img
src="https://cdn.nulab.com/learn-wp/app/uploads/2018/10/14210238/1-Valeria-Pivovarovas-wireframe-example.png"
alt="Wireframe example" width="400" height="200">
</div>
<div class="article-content">
<h2>Wireframe</h2>
<p>A wireframe is the skeleton of your digital project. Think of it as the foundation for your website, app,
or dashboard. It focuses on layout, and content placement-not on colors, fonts, or any visual
polish.<br>Wireframes are your blueprint: a simple, visual guide to quickly lay out your ideas and show how
everything fits together. Before diving into colors, images, or final design details, wireframes help you
map structure and functionality so nothing feels out of place.</p>
</div>
<a href="https://www.experienceux.co.uk/faqs/what-is-wireframing/" class="read-more">Read more</a>

</article>
</main>
<footer>
<p>
This is the default, provided code and no changes have been made yet.
</p>
</footer>
</body>
</html>

<article class="article half">
<div class="image-placeholder">
<img src="https://repository-images.githubusercontent.com/195373656/c5907400-9f96-11e9-9297-099cecb075ca"
alt="Git branch diagram" width="400" height="200">
</div>
<div class="article-content">
<h2>The branch in Git</h2>
<p>In Git, a branch is like a separate workspace where you can make changes and try new ideas without
affecting the main project. Think of it as a "parallel universe" for your code.<br>Branches let you work on
different parts of a project, like new features or bug fixes, without interfering with the main branch. The
common reasons to create a branch are
developing a new feature,fixing a bug, or experimenting with ideas.</p>
</div>
<a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" class="read-more">Read more</a>


</article>
</div>
</main>
<footer>
<ul>
<li><span>© 2026 Fattouma Ouannassi</span></li>
<li><a href="https://codeyourfuture.io">CodeYourFuture</a></li>
</ul>
</footer>
</body>

</html>
176 changes: 100 additions & 76 deletions Wireframe/style.css
Original file line number Diff line number Diff line change
@@ -1,89 +1,113 @@
/* 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;
* {
margin: 0;
padding: 0;
box-sizing: border-box;
font-family: "Segoe UI", Tahoma, Geneva, Verdana, sans-serif;
}
/* ====== Base Elements ======
General rules for basic HTML elements in any context */

body {
background: var(--paper);
color: var(--ink);
font: var(--font);
background-color: #f1f4f5;
color: #000;
line-height: 1.6;
font-size: 16px;
}

header {
max-width: 1200px;
margin: 2rem auto 0;
padding: 2rem 1rem;
background: #eee;
border: 3px solid #ffffff;
text-align: center;
}
a {
padding: var(--space);
border: var(--line);
max-width: fit-content;

header p {
font-style: italic;
font-size: 0.9rem;
letter-spacing: 1px;
margin-top: 0.5rem;
}
img,
svg {

main {
max-width: 1200px;
margin: 2rem auto;
padding: 1rem;
background: #fff;
border: 1px solid #eee;
}

.article {
padding: 20px;
border: 1px solid #eee;
margin-bottom: 20px;
background-color: #eee;
}

.full {
width: 100%;
}

.articles-row {
display: flex;
gap: 20px;
}

.half {
flex: 1;
}

.image-placeholder {
width: 100%;
height: 200px;
background: #eee;
border: 1px solid #eee;
display: flex;
align-items: center;
justify-content: center;
margin-bottom: 1rem;
overflow: hidden;
}

.image-placeholder img {
width: 90%;
height: 95%;
object-fit: cover;
display: block;
}
/* ====== 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;

.article-content h2 {
margin-bottom: 0.5rem;
font-size: 1.2rem;
}
footer {
position: fixed;
bottom: 0;
text-align: center;

.article-content p {
font-size: 0.95rem;
}
/* ====== 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 {

.articles-grid {
display: grid;
grid-template-columns: 1fr 1fr;
gap: var(--space);
> *:first-child {
grid-column: span 2;
}
gap: 1.5rem;
}
/* ====== 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;
}

.read-more {
display: inline-block;
margin-top: 15px;
padding: 10px 18px;
background-color: #eee;
color: #060606;
text-decoration: none;
font-size: 14px;
border-radius: 5px;
transition: background-color 0.3s ease;
border: 2px solid #f7fbfa;
}

footer {
position: fixed;
bottom: 0;
text-align: center;
height: 60px;
background-color: #eee;
width: 100%;
}