Glasgow| 26-ITP-Jan|Fattouma Ouannassi| Sprint 1 | Wireframe/coursework#999
Glasgow| 26-ITP-Jan|Fattouma Ouannassi| Sprint 1 | Wireframe/coursework#999FAprogrammerO wants to merge 2 commits intoCodeYourFuture:mainfrom
Conversation
<!-- You must title your PR like this: Region | Cohort | FirstName LastName | Sprint | Assignment Title For example, London | 25-ITP-May | Carol Owen | Sprint 1 | Alarm Clock Fill in the template below - remove any sections that don't apply. Complete the self checklist - replace each empty box in the checklist [ ] with a [x]. Add the label "Needs Review" and you will get review. Respond to volunteer reviews until the volunteer marks it as "Complete". --> ## Learners, PR Template Self checklist - [x] I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title - [x] My changes meet the requirements of the task - [x] I have tested my changes - [x] My changes follow the [style guide](https://curriculum.codeyourfuture.io/guides/reviewing/style-guide/) ## Changelist This PR includes modifications to the HTML and CSS to create a webpage that follows the provided wireframe layout. The webpage explains the purpose of a README file and the wireframe, aswell as the meaning of a branch in Git, with each topic presented as an article section. ## Questions /
✅ Deploy Preview for cyf-onboarding-module ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jenny-alexander
left a comment
There was a problem hiding this comment.
Hey @FAprogrammerO - you put in some really good work for this wireframe exercise!
There are a few adjustments that should be made, including:
- Can you run your page through W3 validator: https://validator.w3.org/
I see an error in your html and this validator will display it to you. - It's a good idea to format your code so it's easier to read and maintain. You can do this in VSCode, by right-clicking within
index.htmland choosingFormat Document.
Wireframe/index.html
Outdated
| <title>Wireframe to Web Code|Coursework</title> | ||
| <link rel="stylesheet" href="style.css" /> | ||
|
|
||
| <style> |
There was a problem hiding this comment.
According to the exercise acceptance criteria, all of the styling should be done within the CSS file. I see you added styling within the index.html file. Can you make the adjustment?
Wireframe/index.html
Outdated
| <a href="">Read more</a> | ||
| </article> | ||
| </main> | ||
| <section class="article-block"> |
There was a problem hiding this comment.
I noticed you switched out the <article> for <section>. Was there a reason for doing this?
There was a problem hiding this comment.
I switched from article for section to group the articles together, but now after you mentioned that I found out that it wasn't necessary.
| Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, | ||
| voluptates. Quisquam, voluptates. | ||
| </p> | ||
| <a href="">Read more</a> |
There was a problem hiding this comment.
According to the wireframe exercise, each article should have a 'Read more' link (styled as a button) that will bring the user to an article about that topic. Can you add this back?
|
@FAprogrammerO - Great job incorporating code feedback! Your page looks great. 🙌 |
|
Thank you so much @jenny-alexander for your time, and provide such valuable feedback, your suggestions really helped me improve my page 🙏🎉 |

Learners, PR Template
Self checklist
Changelist
This PR includes modifications to the HTML and CSS to create a webpage that follows the provided wireframe layout.
The webpage explains the purpose of a README file and the wireframe, aswell as the meaning of a branch in Git, with each topic presented as an article section.
Questions
/