generated from CodeYourFuture/Module-Template
-
-
Notifications
You must be signed in to change notification settings - Fork 349
London | 25-ITP-September | Carlos Abreu | Sprint 1 | Wireframe #906
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
carlosyabreu
wants to merge
15
commits into
CodeYourFuture:main
Choose a base branch
from
carlosyabreu: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.
Open
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
76d5ce9
Change: all the files in the folder
carlosyabreu ac5bf87
Change style.css file to make the two last images and it's descriptio…
carlosyabreu bd42d00
Made the header and subheader separated
carlosyabreu 671a72c
Applied the change for index.html and style.css to make the webpage s…
carlosyabreu c5489fb
Reframe the code to make the width and height on the containers same …
carlosyabreu d5c2285
Make the content-flex class hidden and delte the background propriety
carlosyabreu 63b9936
Fixed footer section
carlosyabreu c7e007d
Fixed Read more button
carlosyabreu 2a8fa3e
Deleted placeholder.svg and replace with readme-01 file
carlosyabreu 2eccf39
Add alt comment to the 1st image
carlosyabreu 8e94a7e
Fixed </br> and <br/> errors
carlosyabreu 0f1687c
Fixed summary element putting it inside detail tag as it's more appro…
carlosyabreu 8bdec68
Change readme to README
carlosyabreu 5798088
Change the file so it passes w3validator check
carlosyabreu 74ee279
Both images bellow the top are aligned horizontally
carlosyabreu 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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,116 @@ | ||
| <!DOCTYPE html> | ||
| <html lang="en"> | ||
| <head> | ||
| <meta charset="UTF-8" /> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0" /> | ||
| <meta charset="UTF-8"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>Wireframe</title> | ||
| <link rel="stylesheet" href="style.css" /> | ||
| <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. | ||
| </p> | ||
| <h1>Fork of CodeYourFuture</h1> | ||
| <p>Wireframe Project</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> | ||
| <!-- ✅ Section 1 with proper heading --> | ||
| <div class="top"> | ||
| <section class="article"> | ||
| <h2>README Overview</h2> | ||
| <article> | ||
| <img src="readme-01.png" alt="README illustration"> | ||
| <h3>What is the purpose of a README file?</h3> | ||
| <details> | ||
| <summary>Readme in a few words</summary> | ||
| <p> | ||
| The README file is used to explain what files are included and how | ||
| the project can be installed or used. It allows the owner to add | ||
| images and videos to help the reader navigate the project. A | ||
| well-written README helps users or developers understand the | ||
| project's structure and can attract more contributors. | ||
| </p> | ||
| </details> | ||
| <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> | ||
| </section> | ||
| </div> | ||
|
|
||
| <!-- ✅ Layout div (no heading needed) --> | ||
| <div class="grid-branch-container"> | ||
| <div class="grid"> | ||
| <!-- ✅ Section 2 with heading --> | ||
| <section class="article"> | ||
| <h2>Wireframe Overview</h2> | ||
| <article> | ||
| <img src="wireframe.png" alt="Wireframe illustration"> | ||
| <h3>What is the purpose of a wireframe?</h3> | ||
| <details> | ||
| <summary>Wireframe explanation in a nutshell</summary> | ||
| <p> | ||
| A wireframe is a simple blueprint of a webpage or app. It focuses | ||
| on structure and layout, showing where elements like images, | ||
| text, and buttons will go before visual design begins. | ||
| </p> | ||
| <p> | ||
| The purpose of a wireframe in web design is to serve as a | ||
| skeletal blueprint, mapping out a website's layout, structure, | ||
| and core functionality before any visual design is applied. This | ||
| allows designers to plan the user experience, refine the site | ||
| architecture, and communicate the project's direction to | ||
| stakeholders efficiently and cost-effectively. | ||
| </p> | ||
| </details> | ||
| <a | ||
| href="https://www.digitalsilk.com/digital-trends/what-is-a-wireframe/" | ||
| target="_blank" | ||
| >Read more</a | ||
| > | ||
| </article> | ||
| </section> | ||
| </div> | ||
|
|
||
| <!-- ✅ Section 3 with heading --> | ||
| <div class="branch"> | ||
| <section class="article"> | ||
| <h2>Git Branch Overview</h2> | ||
| <article> | ||
| <img src="git-branch.png" alt="Git branch illustration"> | ||
| <br> | ||
| <br> | ||
| <h3 style="margin-top: 15px;">What is a branch in Git?</h3> | ||
| <details> | ||
| <summary>Git branch and what it means</summary> | ||
| <p> | ||
| A branch in Git allows developers to work on new features or | ||
| fixes separately from the main codebase. This makes | ||
| collaboration easier and ensures the main project stays stable | ||
| while changes are tested. | ||
| </p> | ||
| <p> | ||
| In other words, a Git branch is an independent line of | ||
| development that allows developers to experiment without | ||
| affecting the stable version. Branches enable collaboration, | ||
| experimentation, and version control by letting multiple | ||
| developers work simultaneously. | ||
| </p> | ||
| </details> | ||
| <a | ||
| href="https://www.w3schools.com/git/git_branch.asp" | ||
| target="_blank" | ||
| >Read more</a | ||
| > | ||
| </article> | ||
| </section> | ||
| </div> | ||
| </div> | ||
| </main> | ||
|
|
||
| <footer> | ||
| <p> | ||
| This is the default, provided code and no changes have been made yet. | ||
| </p> | ||
| <p>This is the footer of the wireframe project.</p> | ||
| </footer> | ||
| </body> | ||
| </html> | ||
This file was deleted.
Oops, something went wrong.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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.
The footer requirements state that it should be 'fixed'. This means that no matter where you scrolls on the page (up, down), the footer will always be visible. Can you make this change?