Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

This is a blog preview card I made and made it responsive

Fastcheettahh• 20

@fastcheetah

Desktop design screenshot for the Blog preview card coding challenge

This is a solution for...

  • HTML
  • CSS
1newbie
View challenge

Design comparison


SolutionDesign

Solution retrospective


What are you most proud of, and what would you do differently next time?

I used a different way when laying out my work and I think it will be very helpful in the future

What challenges did you encounter, and how did you overcome them?

I know more about my areas of weakness and I am trying my best to solve them like I specifically have problems with flex and box models and im trying to fix them

What specific areas of your project would you like help with?

If you have problems with the site please feel free to comment

Community feedback

P
Grace• 27,870

@grace-snow

Posted

I think the most important place for you to focus your learning is on HTML at the moment. This needs some important changes, essential for accessibility, SEO and usability.

  1. You only need to use the figure element if you need a figcaption. It is not a generic wrapper for all images. These images don't need a wrapping element at all, but you can use a div when the only reason is for layout purposes.
  2. Make sure you know how and when to write alt text on images. There is a great post about this in the resources channel on discord (search for "Alt" and you'll find it).
  3. Headings must be used appropriately. Learning is not a heading, nor is Greg's name. Heading tags must only be used when the text is an actual title for some content around it.
  4. Also, it's essential that headings are in the correct order. On a full Web page the headings list should act like a table of contents in a book or long document — reading it communicates the structure of the document (in this case web page) and relationships between content, and allows people to jump to the content they want. Every page has a h1 as the title of the page and then other headings below are sequential. In this case, because it's only a single component challenge, you don't need a h1, just a h2 for the blog title as you have already.
  5. This component would be unusable on a real site. There is no way at the moment for users to access the blog it's signposting to, because you've not included a link anywhere. There should be an anchor within the h2, wrapping the blog title text. This is what makes the card interactive to all users (eg including keyboard)
  6. Once you've added that link you'll need to make the whole card clickable in this case. That is not always the case, but we know the whole card is meant to be clickable in this because the design includes hover styles for the whole card. Always take note of where you see hover styles — that means something is meant to be interactive. To do this, you will need to make the card position relative and then add a pseudo element on the anchor inside the heading. That pseudo should be positioned absolutely and full height and width so it covers the whole card, effe tively making the link take up more space so the whole card becomes clickable even though the link is only small inside that card.
0

P
Grace• 27,870

@grace-snow

Posted

In the css I have some more tips for you 😊

  1. Get into the habit of including a full modern css reset at the start of the styles in every project. Andy Bell or Josh Comeau both have good ones you can look up and use.
  2. The card must not have a width, especially not in pixels . Give it a max width in rem instead. This makes the card immediately responsive because it can shrink when necessary (eg on smaller screens) and the layout will work for all users, even those who change their default text size.
  3. Don't use large margins to try and center a component on the screen. Keep margins and paddings small and use an alternative. For example, I recommend on single component demos like this, to make the body into a flex column with min-height 100svh and flex properties on it to center its children.
  4. Try not to use element selectors especially not generic ones like divs. This increases css specificity for no reason, makes the styles hard to read and maintain, and means you couldn't lift this component out and use it in a real site. (Because compone nt specific styling is on a div or figure. Place classes in what you want to style.
  5. You can delete all media queries from this. This component does not need any.

Marked as helpful

0
Fastcheettahh• 20

@fastcheetah

Posted

@grace-snow Thank you I never knew of the advantages of rem and it could be responsive in a site.

0

Please log in to post a comment

Log in with GitHub
Discord logo

Join 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