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
Binary file added Wireframe/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.
130 changes: 103 additions & 27 deletions Wireframe/index.html
Original file line number Diff line number Diff line change
@@ -1,33 +1,109 @@
<!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>
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Understanding README Files, Wireframes and Git Branches</title>
<link rel="stylesheet" href="style.css">
</head>

<body>
<header>
<h1>Understanding README Files, Wireframes and Git Branches</h1>

<p>
This article explores three important concepts used in software
development: README files, Wireframes and Git branches.
</p>

<p>
Code adapted and changed by Juanita.
</p>
</header>

<main>

<article>
<h2>What is a README File?</h2>

<img src="readme.png" alt="README file example">

<p>
This is the default, provided code and no changes have been made yet.
A README file is usually the first document people see when they visit a
project. It provides an overview of the project, explains its purpose,
gives installation instructions and helps users understand how to use
the software.
</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.
A well-written README makes it easier for developers and contributors
to understand and work with a project.
</p>
</footer>
</body>
</html>

<a
href="https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/"
target="_blank"
rel="noopener noreferrer"
>
Learn more about README files
</a>
</article>

<article>
<h2>What is a Wireframe?</h2>

<img src="wireframe.png" alt="Website wireframe example">

<p>
A wireframe is a simple visual representation of a webpage or
application. It focuses on structure and layout rather than colours,
images or final design elements.
</p>

<p>
Fun fact: designers use wireframes to plan where content, navigation and key
features will appear before development begins.
</p>

<a
href="https://balsamiq.com/blog/what-are-wireframes/"
target="_blank"
rel="noopener noreferrer"
>
Learn more about wireframes
</a>
</article>

<article>
<h2>What is a Git Branch?</h2>

<img src="git-branch.png" alt="Git branch diagram">

<p>
A Git branch is an independent line of development within a Git
repository. It allows developers to work on new features, bug fixes or
experiments without affecting the main version of the project.
</p>

<p>
Once the work is complete and tested, the branch can be merged back into
the main codebase.
</p>

<a
href="https://www.atlassian.com/git/tutorials/using-branches"
target="_blank"
rel="noopener noreferrer"
>
Learn more about Git branches
</a>
</article>

</main>

<footer>
<p>Created for CYF Wireframe assessment by Juanita Nwachukwu.</p>
</footer>

</body>
</html>
Binary file added Wireframe/readme.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
26 changes: 19 additions & 7 deletions Wireframe/style.css
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ As well as useful links to learn more */
====== Design Palette ====== */
:root {
--paper: oklch(7 0 0);
--ink: color-mix(in oklab, var(--color) 5%, black);
--ink: black;
--font: 100%/1.5 system-ui;
--space: clamp(6px, 6px + 2vw, 15px);
--line: 1px solid;
Expand All @@ -30,6 +30,7 @@ body {
background: var(--paper);
color: var(--ink);
font: var(--font);
padding-bottom: 60px;
}
a {
padding: var(--space);
Expand All @@ -48,11 +49,18 @@ https://www.w3.org/WAI/tutorials/page-structure/regions/
main {
max-width: var(--container);
margin: 0 auto calc(var(--space) * 4) auto;

header {
text-align: center;
}

footer {
position: fixed;
bottom: 0;
left: 0;
width: 100%;
text-align: center;
background: var(--paper);
}
/* ====== Articles Grid Layout ====
Setting the rules for how articles are placed in the main element.
Expand All @@ -65,10 +73,12 @@ main {
display: grid;
grid-template-columns: 1fr 1fr;
gap: var(--space);
> *:first-child {
}

main > *: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.
Expand All @@ -80,10 +90,12 @@ article {
text-align: left;
display: grid;
grid-template-columns: var(--space) 1fr var(--space);
> * {
}

article > * {
grid-column: 2/3;
}
> img {

article > img {
grid-column: span 3;
}
}
}
Comment on lines +99 to +101
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code is not yet consistently indented.

Could you look up the benefits of using a code formatter? I strongly recommend following this guide
to enable VS Code's "Format on Save" option or use its "Format Document" command. This will help ensure your code is consistently formatted and easier to read and maintain.

Loading