-
-
Notifications
You must be signed in to change notification settings - Fork 432
Sheffield | 26-ITP-January | Connor Parsons | Sprint 1 | Wireframe #1178
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
base: main
Are you sure you want to change the base?
Changes from 9 commits
9297087
5ee959e
0717994
45aace1
70d6106
cb2c56d
ef1f534
f1d57f0
d4157c4
8663cfb
504aeff
1f2d33c
711ee39
4c87e51
9731ecf
b2d2529
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,33 +1,70 @@ | ||
| <!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" /> | ||
| <meta charset="UTF-8"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>Three Key Tech Tips</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. | ||
| <h1>Three Tech Tips</h1> | ||
| <p id="p_description"> | ||
| Here are some useful things to know when learning to create your own websites | ||
| and manage tech projects. | ||
| </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. | ||
| <img src="https://repository-images.githubusercontent.com/190038729/991a8980-8e28-11e9-9d4f-b0bdf64180f4" alt="Readme"> | ||
| <h2>The Purpose of a Readme File</h2> | ||
| <p id="p_readme"> | ||
| A readme file is a very important part of any GitHub repository. It is often the first item a visitor will see | ||
| when landing on a repository. A readme file should provide users with information about the purpose of a | ||
| project, how to use it effectively and who the contributers and maintainers of the project are. | ||
| </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" | ||
| target="_blank">Read More</a> | ||
| </article> | ||
| <article> | ||
| <h2> | ||
| The Purpose of A Wireframe | ||
| </h2> | ||
| <img src="https://cdn.nulab.com/learn-wp/app/uploads/2018/10/14210245/Cacoo-8-must-see-wireframes-680x450-1.png" alt="Wireframe"> | ||
| <p> | ||
| A wireframe in web design is a basic visual representation of a webpage | ||
| that helps to outline its overall stucture and functionality. | ||
| Wireframes are used early in the development process to demonstrate the basic | ||
| structure of a page before visual design and content are added. The simplicity | ||
| of wireframes allow for changes and iterations to be made quickly and easily. | ||
| </p> | ||
| <a href="https://www.experienceux.co.uk/faqs/what-is-wireframing/" | ||
| target="_blank">Read More</a> | ||
| </article> | ||
| <article> | ||
| <h2> | ||
| What is a Git Branch | ||
| </h2> | ||
| <img src="https://media.licdn.com/dms/image/v2/D4D12AQH6ykM-AVoDKg/article-cover_image-shrink_720_1280/B4DZZW5EzAHAAM-/0/1745214525491?e=2147483647&v=beta&t=kB_Gy_FceQSnp1FMZ2lVvoPis3lrcCQjgX0Zur3z4pc" | ||
| alt="Git Branch Model"> | ||
| <p> | ||
| A git branch is a pointer to a snapshot of all the changes that occured | ||
| on that branch. Upon creating a new GitHub repository you will usually | ||
| be on the main branch by default. You can create additional branches which | ||
| are like separate workspaces to make changes to a project or test other features | ||
| without compromising the base project. Branches are useful when working | ||
| on a project with many collaborators as each individual can make changes on their own local | ||
| copy of a project and propose their changes to be integrated to the main branch | ||
| after approval. | ||
| </p> | ||
| <a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" | ||
| target="_blank">Read More</a> | ||
| </article> | ||
| </main> | ||
| <footer> | ||
| <p> | ||
| This is the default, provided code and no changes have been made yet. | ||
| </p> | ||
| </footer> | ||
| <footer> | ||
| <p id="p_footer"> | ||
| Footer content will go here | ||
| </p> | ||
| </footer> | ||
| </body> | ||
| </html> | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -22,15 +22,35 @@ As well as useful links to learn more */ | |
| --font: 100%/1.5 system-ui; | ||
| --space: clamp(6px, 6px + 2vw, 15px); | ||
| --line: 1px solid; | ||
| --line2: 5px solid; | ||
| --container: 1280px; | ||
| } | ||
|
|
||
|
|
||
| /* ====== Base Elements ====== | ||
| General rules for basic HTML elements in any context */ | ||
| body { | ||
| background: var(--paper); | ||
| color: var(--ink); | ||
| font: var(--font); | ||
| } | ||
| h1 { | ||
| text-align: center; | ||
| font-size: 50px; | ||
| } | ||
| h2 { | ||
| text-align: center; | ||
| font-size: 30px; | ||
|
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. Using relative units for font size (e. g., |
||
| } | ||
|
|
||
| #p_readme { | ||
| text-align: left; | ||
| font-size: 22px; | ||
| } | ||
| #p_description { | ||
| text-align: center; | ||
| font-size: 26px; | ||
| } | ||
|
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.
Can you think of more appropriate names that are more descriptive and are independent of article content? Alternatively, you can use complex selectors to select the specific |
||
| a { | ||
| padding: var(--space); | ||
| border: var(--line); | ||
|
|
@@ -50,8 +70,14 @@ main { | |
| margin: 0 auto calc(var(--space) * 4) auto; | ||
| } | ||
| footer { | ||
| border: var(--line); | ||
| position: fixed; | ||
| bottom: 0; | ||
| bottom: -2px; | ||
| left: 50%; | ||
| transform: translateX(-50%); | ||
| width: 1280px; | ||
| background-color: rgb(202, 160, 160); | ||
| border-color: black; | ||
| text-align: center; | ||
| } | ||
| /* ====== Articles Grid Layout ==== | ||
|
|
||
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.
Indentation is slightly off.
It is a good practice to use an code formatting tool such as VSCode's "Format Document" to keep our code consistently formatted before we commit the changes.
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.
Ok thanks that's a good feature to know about.