-
-
Notifications
You must be signed in to change notification settings - Fork 494
London | 26-ITP-May | Edina Kurdi | Sprint 2 | Wireframe #1357
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
edinakurdi
wants to merge
11
commits into
CodeYourFuture:main
Choose a base branch
from
edinakurdi:feature/wireframe
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+84
−49
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0a4362f
add placeholder text to wireframe articles
edinakurdi ceb09d7
update link styling, footer content and article links
edinakurdi 0515ff4
add space before footer link
edinakurdi aac134f
remove dubplicate padding on a
edinakurdi 6844c6c
clean up footer CSS
edinakurdi 8c86b9f
add colour variable to CSS root
edinakurdi 33516ee
add and style article images
edinakurdi c0c0492
add short descriptions of the three concepts
edinakurdi 7033ccf
fix footer according to criteria - fixed position
edinakurdi d5fb5bf
readme checks each criteria
edinakurdi 570b39b
add wireframe alt text
edinakurdi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,33 +1,54 @@ | ||
| <!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>Wireframe</title> | ||
| <link rel="stylesheet" href="style.css" /> | ||
| </head> | ||
|
|
||
| <body> | ||
| <header> | ||
| <h1>Developer essentials</h1> | ||
| <p> | ||
| A quick introduction to READMEs, wireframes, and Git branches. | ||
| </p> | ||
| </header> | ||
| <main> | ||
| <article> | ||
| <img src="https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frb46gni0wl2759llb6xs.png" alt="readme file" /> | ||
| <h2>What is a README file?</h2> | ||
| <p> | ||
| This is the default, provided code and no changes have been made yet. | ||
| A README is often what people look at in a project to understand what it is about. It should include a description of the project, instructions on how to use it, and any additional information that may be useful. | ||
| </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> | ||
| <a href="https://www.makeareadme.com/" target="_blank">Read more</a> | ||
| </article> | ||
|
|
||
| <article> | ||
| <img src="https://live.staticflickr.com/2154/5734993652_d4a2ee8778_b.jpg" alt="wireframe sketch of website layout" /> | ||
| <h2>What is the purpose of a wireframe?</h2> | ||
| <p> | ||
| This is the default, provided code and no changes have been made yet. | ||
| A wireframe for a website is like a blueprint for a house. It is a visual representation of the layout of the website. It is useful for planning purposes and can save time before building, by helping us spot potential issues early. | ||
| </p> | ||
| </footer> | ||
| </body> | ||
| </html> | ||
| <a href="https://balsamiq.com/blog/what-are-wireframes/" target="_blank">Read more</a> | ||
| </article> | ||
|
|
||
| <article> | ||
| <img src="https://blog.nobledesktop.com/_next/image?url=%2Fimages%2Fblog%2Fgit-branches%2Fgit-branches-merge.png&w=750&q=75" alt="git branching diagram" /> | ||
| <h2>What is a branch in Git?</h2> | ||
| <p> | ||
| A branch in Git is like an alternative version of a project. When several developers work on the same project, separate branches help them avoid overriding each other's work. These branches then can be merged into the main branch through a pull request. | ||
| </p> | ||
| <a href="https://www.geeksforgeeks.org/git/introduction-to-git-branch/" target="_blank">Read more</a> | ||
| </article> | ||
|
|
||
| </main> | ||
| <footer> | ||
| <p> | ||
| This page was built following a provided wireframe design: <a href="https://github.com/edinakurdi/Module-Onboarding/blob/main/Wireframe/README.md">Wireframe</a> | ||
| </p> | ||
| </footer> | ||
| </body> | ||
|
|
||
| </html> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,8 +18,10 @@ As well as useful links to learn more */ | |
| ====== Design Palette ====== */ | ||
| :root { | ||
| --paper: oklch(7 0 0); | ||
| --color: white; | ||
| --ink: color-mix(in oklab, var(--color) 5%, black); | ||
| --font: 100%/1.5 system-ui; | ||
| /* increased font size, since it felt tiny */ | ||
| --font: 1.15rem/1.5 system-ui; | ||
| --space: clamp(6px, 6px + 2vw, 15px); | ||
| --line: 1px solid; | ||
| --container: 1280px; | ||
|
|
@@ -32,28 +34,40 @@ body { | |
| font: var(--font); | ||
| } | ||
| a { | ||
| padding: var(--space); | ||
| padding: 4px 20px; | ||
| border: var(--line); | ||
| max-width: fit-content; | ||
| max-width: fit-content; | ||
| text-decoration: none; | ||
| font-weight: bold; | ||
| } | ||
| img, | ||
| svg { | ||
| img { | ||
| width: 100%; | ||
| object-fit: cover; | ||
| height: 350px; | ||
| filter: grayscale(70%) ; | ||
| } | ||
| /* ====== Site Layout ====== | ||
| Setting the overall rules for page regions | ||
| https://www.w3.org/WAI/tutorials/page-structure/regions/ | ||
| */ | ||
| header { | ||
| text-align: center; | ||
| } | ||
| main { | ||
| max-width: var(--container); | ||
| margin: 0 auto calc(var(--space) * 4) auto; | ||
| padding: 0 8rem; | ||
| } | ||
|
Comment on lines
56
to
60
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is another |
||
| footer { | ||
| position: fixed; | ||
| bottom: 0; | ||
| width: 100%; | ||
| text-align: center; | ||
| } | ||
| footer a { | ||
| padding: 2px; | ||
| border: none | ||
| } | ||
| /* ====== 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 | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Breaking HTML text into multiple lines helps make the code easier to read, edit, and maintain while preserving the same rendered output.
VS Code formatter could be used to keep our code consistently formatted, including breaking long
lines of HTML text into multiple lines for easier editing and maintenance.
As a best practice, consider following this guide to enable VS Code's
"Format on Save" option or to use its "Format Document" command to ensure your code is always consistently formatted.