Skip to content

London | May-2025 | Mo Muchunu | Wireframe To Web Code #427

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.

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
wants to merge 12 commits into
base: main
Choose a base branch
from
85 changes: 73 additions & 12 deletions Wireframe/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,30 +3,91 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="description" content="web development guide,README files,wireframes,git branches" />
<title>Wireframe</title>
<link rel="stylesheet" href="style.css" />
</head>
<body>
<header>
<h1>Wireframe</h1>

<header>
<h1>Web Dev Basics</h1>
<h2>README Files, Wireframes, and Git Branches Explained</h2>
</header>

<main>

<div id="first">

<article>
<h2> What is the purpose of a README file?</h2>

<p>
This is the default, provided code and no changes have been made yet.
A README file is usually the first file a user sees when they open a project,<br>
and acts as a guide for anyone who wants to understand or contribute to the project.</p>

<p>
<strong>A README file should include:</strong>
</p>
</header>
<main>
<ul>
<li>What the project does.</li>
<li>Why the project is useful.</li>
<li>How to install and use the project.</li>
<li>Where to find help on a project.</li>
<li>Information on who maintains and contributes to the project.</li>
</ul>

<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"
target="_blank">More about READMEs</a>

<div id="image-container">
<img src="https://logowik.com/content/uploads/images/github9775.jpg" alt="Github logo">
</div>

</div>
</article>

<article>
<img src="placeholder.svg" alt="" />
<h2>Title</h2>
<h2>What is the purpose of a Wireframe?</h2>
<p>
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
voluptates. Quisquam, voluptates.
</p>
<a href="">Read more</a>
A wireframe is a simple layout of an app or website that shows the structure and key features.
It's used early in design to plan how users will interact with the page before adding visuals and content.</p>
<p>
<strong>The three main purposes of wireframes are:</strong>
<ol>
<li>To keep the design focused on the user.</li>
<li>Identify potential problems by making features and navigation clear.</li>
<li>A low-cost way to test ideas because they are quick to create.</li>
</ol>
</p>

<p>
Wireframes can be created using paper and pencil, or with software like Figma, Sketch, or Adobe XD.</p>
<a href="https://www.productplan.com/glossary/wireframe/"
target="_blank">More about Wireframes</a>
</article>

<article>
<h2>What is a branch in Git?</h2>
<p>
A branch in Git is a separate line of development in a project.<br>
It’s created from another branch, usually the main one, so you can make changes without affecting the rest of the project.</p>

<p>
Each branch is like a copy of the project where you can work on different versions of a project at the same time.</p>

<p>
<ul>
<li>Branches are useful for teams working on the <strong>same</strong> project.</li>
<li>You can create a <strong>new branch</strong> for features, bug fixes, or experiments, and then merge them back into the main branch when they're ready.</li>
</ul>
</p>

<a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches"
target="_blank">More about Git Branches</a>
</main>
<footer>
<p>
This is the default, provided code and no changes have been made yet.
By Mo Muchunu
</p>
</footer>
</body>
Expand Down
149 changes: 80 additions & 69 deletions Wireframe/style.css
Original file line number Diff line number Diff line change
@@ -1,89 +1,100 @@
/* 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;
--ink: black;
--font-serif: "Serif", Georgia;
--space: clamp(6px, 6px + 2vw, 15px);
--line: 1px solid;
--container: 1280px;
--container: 1300px;
}
/* ====== Base Elements ======
General rules for basic HTML elements in any context */

body {
background: var(--paper);
color: var(--ink);
font: var(--font);
background-color: rgb(35, 35, 35);
display: grid;
place-content: center;
font: var(--font-serif);
}

a {
padding: var(--space);
border: var(--line);
max-width: fit-content;
}
img,
svg {
width: 100%;
object-fit: cover;

a:hover {
background-color: rgba(125, 122, 122, 0.5);
color: var(--ink);
text-decoration: none;
border-radius: 10px;
}
/* ====== 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;

h1 {
font-size: 90px;
font-weight: 800;
}
footer {
position: fixed;
bottom: 0;
text-align: center;

h2 {
font-size: 30px;
font-weight: 500;
}

header {
text-align: center;
color: rgb(255, 255, 255);
padding: 10px;
margin-bottom: 10px;
border: 4px solid rgba(255, 255, 255, 0.5);
border-radius: 10px;
background-color: black;
max-width: var(--container);
}
/* ====== 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/
*/

#first {
grid-column: 1 / span 2;
padding: 20px;

}
#image-container {
display: flex;
justify-content: right;
position: absolute;
top: 400px;
right: 200px;
z-index: 1;
}

img {
width: 500px;
height: auto;
}

article {
background-color: rgba(255, 255, 255);
padding: 40px;
border-radius: var(--space);
font-size: 17px;
text-align: justify;
display: grid;
}


main {
max-width: var(--container);
margin: 0 auto calc(var(--space) * 4) auto;
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 {
bottom: 0;
text-align: center;
padding: var(--space);
color: white;
}