Skip to content
Open
Binary file added Wireframe/images/How-To-Create-a-Git-Branch.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added Wireframe/images/low-to-final.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added Wireframe/images/readme.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
40 changes: 32 additions & 8 deletions Wireframe/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -10,23 +10,47 @@
<header>
<h1>Wireframe</h1>
<p>
This is the default, provided code and no changes have been made yet.
The purpose of this project is to take a wireframe and express it in web code.
</p>
</header>
<main>
<article>
<img src="placeholder.svg" alt="" />
<h2>Title</h2>
<img src="images/readme.png" alt="an image depicting a GitHub logo addressing how to write a readme" />
<h2>What is the purpose of a README file?</h2>
<p>
Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
voluptates. Quisquam, voluptates.
A README file gives readers a quick, clear understanding of a project.
It explains what the project does, why it exists, and how to use it.
In most cases, it includes setup steps, usage examples, and guidance for anyone who wants to contribute.
It’s essentially the project’s introduction and user manual in one place.

</p>
<a href="">Read more</a>
<a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes" class ="btn">Read more</a>
</article>
</main>
<article>
<img src="images/low-to-final.png" alt="an image depicting a wireframe from a low level design to a high level design" />
<h2>What is the purpose of a wireframe?</h2>
<p>
A wireframe shows the basic layout of a website or app before any design work begins.
Its purpose is to map out structure, content placement, and user flow so teams can agree
on functionality early, avoid costly changes later, and create a clear blueprint for the final design.

</p>
<a href="https://www.productplan.com/glossary/wireframe/" >Read more</a>
</article>
<article>
<img src="images/How-To-Create-a-Git-Branch.png" alt="an image of git branch and its commit history" />
<h2>What is a branch in Git?</h2>
<p>
A branch in Git is an independent line of development that lets you work on new features
or fixes without affecting the main codebase. It creates a safe space to experiment, collaborate,
and make changes, which can later be merged back into the main project when ready.
</p>
<a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" >Read more</a>
</article>
</main>
<footer>
<p>
This is the default, provided code and no changes have been made yet.
&copy: Website made by Martha ❤️
</p>
</footer>
</body>
Expand Down
47 changes: 44 additions & 3 deletions Wireframe/style.css
Original file line number Diff line number Diff line change
Expand Up @@ -27,32 +27,73 @@ As well as useful links to learn more */
/* ====== Base Elements ======
General rules for basic HTML elements in any context */
body {
background: var(--paper);
--body-background: oklch(7 0 0);
--body-space: clamp(16px, 16px + 8vw, 60px);
background: var(--body-backgroung);
color: var(--ink);
font: var(--font);
padding: var(--body-space);

}
a{
--text-color: white;
}
a {
color: var(--text-color);
padding: var(--space);
border: var(--line);
max-width: fit-content;
text-decoration: none;
border-radius: 10px;
background-color:#cf2e2e;
font-weight:bold;



}
img,
svg {
width: 100%;
object-fit: cover;

}
/* ====== Site Layout ======
Setting the overall rules for page regions
https://www.w3.org/WAI/tutorials/page-structure/regions/
*/
header{
text-align: center;
color: #cf2e2e;

/* cadetblue */
}
h1{
text-transform: uppercase;
}

p{
--paragraph-font: 100%/2 Arial, Helvetica, sans-serif;
color: #6c6c89;
font: var(--paragraph-font);
}
main {
max-width: var(--container);
margin: 0 auto calc(var(--space) * 4) auto;

}
footer {
position: fixed;
bottom: 0;
left: 0;
text-align: center;
border-top: var(--line);
width: 100%;
background:oklch(0.07 0 0);
padding: 1rem;

}
footer{

> *:first-child{color: azure;
font-weight: bold;}
}
/* ====== Articles Grid Layout ====
Setting the rules for how articles are placed in the main element.
Expand Down