Manchester| 26-ITP-May | John Robinson | Sprint 2 | Wireframe#1422
Manchester| 26-ITP-May | John Robinson | Sprint 2 | Wireframe#1422JohnRob-jnr wants to merge 3 commits into
Conversation
✅ Deploy Preview for cyf-onboarding-module ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
cjyuan
left a comment
There was a problem hiding this comment.
Code is error-free and page layout matches the wireframe well. Good job! It would probably match the wireframe better if all articles have the same padding space.
-
One of the acceptance criteria, "The page footer is fixed to the bottom of the viewport", has not yet been satisfied. Can you make the necessary change? (Suggestion: Ask AI what that requirement means).
-
I noticed some typo. Could you run the page content through an AI tool to identify any potential improvements, even minor ones, to help ensure the content is fully polished?
| section { | ||
| border: var(--line); | ||
| padding-bottom: var(--space); | ||
|
|
||
| text-align: left; | ||
| display: grid; | ||
| grid-template-columns: var(--space) 1fr var(--space); | ||
| > * { | ||
| grid-column: 2/3; | ||
| } | ||
| > img { | ||
| img { | ||
| width: 100%; | ||
| grid-column: span 3; | ||
| } |
There was a problem hiding this comment.
Indentation is off.
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.
| </article> | ||
| <section> | ||
| <img src="./img/readmeimg.png" alt="README File" /> | ||
| <h3>README File</h3> |
There was a problem hiding this comment.
-
Currently, the first item is an
<article>while the other two are<section>elements. Since all three are standalone pieces of content with their own heading, description, image, and link, they should probably all be<article>elements. -
Since all three topics are siblings, they should use the same heading level.
|
Can you also restore the "Changelist" header in the PR description? It should be a level 2 header that looks like this: Changelist |

Manchester| 26-ITP-May | John Robinson | Sprint 2 | Wireframe
Resubmitted my Wireframe as I made an error when working on it previously that would not allow it to be submitted for a pull request