Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Blog Preview Card

Omarhdez-218•30
@Omarhdez-218
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I had a difficult time getting the name "Greg Hopper" & the avatar picture side by side. I overcame that problem by adding a display of inline-block & vertical aligining it to the middle on "Greg Hopper".

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ken•160
    @ubcyukiny
    Posted 9 months ago

    Hello!

    Great work on finishing the challenge!

    There are some minor differences from the design:

    1. Category background color is off, you could refer back to the Figma design system to get the RGB value

    2. The author section is not aligned with the content, I see you have some paddings in the author section, maybe that could affect the alignment. I suggest using chrome dev tools by clicking on inspect, click on the div you want to inspect, and computed, you will see the margins, padding, and div size highlighted, makes it easier to figure out what is off.

    Also look into responsive web design, the dimensions of the blog preview card should change as the screen max width gets smaller, to give a better experience viewing using a phone. In the Figma design, you could inspect the width, height, font size changes.

    Here is a short video about it

    Marked as helpful
  • Adabe4•60
    @Adabe4
    Posted 9 months ago

    Try to be more careful with the font-size and the colors. The "published" text looks way more bold in your solution than in the design and the learning-box should have the same color as the background. Otherwise your solution is close to the design.

    Marked as helpful

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub