Design comparison
Solution retrospective
I am very proud of myself for achieving the task in a short time.
What challenges did you encounter, and how did you overcome them?The challenges are still the same. I am still struggling with responsiveness.
What specific areas of your project would you like help with?The responsiveness of my website.
Community feedback
- @Islandstone89Posted 7 months ago
HTML:
-
Every webpage needs a
<main>
that wraps all of the content, except for<header>
andfooter>
. This is vital for accessibility, as it helps screen readers identify a page's "main" section. Wrap the card in a<main>
, and change.main
to.card
. -
Replace the
id
with aclass
. -
"Learning" is a
<p>
. -
Wrap the date in a
<time>
element:<p>Published <time datetime="2023-12-21">21 Dec 2023</time></p>
. -
The heading would have a link as this is a blog card.
-
An appropriate alt text for the profile image would be "Headshot of Gary Hooper".
-
"Gary Hooper" is a
<p>
.
CSS:
-
Including a CSS Reset at the top is good practice.
-
Add around
1rem
ofpadding
on thebody
, so the card doesn't touch the edges on small screens. -
Remove the margin on the card.
-
To center the card horizontally and vertically, use Flexbox on the body:
display: flex; flex-direction: column; justify-content: center; align-items: center; min-height: 100svh;
-
Except for the profile image, remove all widths and heights.
-
Add a
max-width
of around20rem
on the card, to prevent it from getting too wide on larger screens. -
Remove
font-style: normal
, as that is the default value already. -
Add
display: inline-block
orwidth: fit-content
on "Learning". -
font-size
must never be in px. This is a big accessibility issue, as it prevents the font size from scaling with the user's default setting in the browser. Use rem instead. -
Paragraphs have a default value of
font-weight: 400
, so there is no need to declare it. -
It is standard practice to add
display: block
andmax-width: 100%
on images - the max-width makes images resize according to their container. -
As the design doesn't change, there is no need for any media queries. When you do need them, they should be in rem, not px. Also, it is common practice to do mobile styles first and use media queries for larger screens.
Marked as helpful0@maryam-damagumPosted 2 months agoVery helpful, I really appreciate your comments. Thank you very much @Islandstone89
1 -
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord