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

Flexbox, Mobile First Design, Utility Classes

accessibility
Adeleke Bright•40
@adeisbright
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

Using my knowledge from previous challange to build the page following mobile first approach.

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

I encountered challenges with the box-shadow effect and also typography for the contents

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

Box Shadow and Typography

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • ElDonPapa•50
    @ElDonPapa
    Posted 5 months ago

    Good job completing your second project! It's nice, and I see you mainly used responsive CSS values for your page, which is a great thing.

    The link to your github repo is not working so I'll do based on what I get in the browser.

    Considering your trouble with typography, it seems mostly good, the only thing that makes it really differ from the design is the line-height. In the original design, a line-height of 150% is used on almost everything.

    Secondly, your box-shadow is almost good, the problem is just with your y-offset that should be the same as the x-offset, so you would end up with (just an example):

    box-shadow: 8px 8px hsl(0 0 7); 
    

    There are also some problems with your html semantic, such as your use of <section> tags to separate the content of the card, or also your use of an <h3> tag when there are no other headings, in practice, you should avoid skipping heading levels (so starting with <h1> then using <h2>...)

    Here is a great article talking about just that if you want to dive deeper. (I also recommend checking there other articles, they are really helpful!)

    Overall, I feel like you maybe have overlooked some aspects of the design, you should really capitalize on the figma file that we are given as a starter for everything, especially values like spacings.

    But appart from that, it's not bad! I hope I could have helped you at least a little bit 🙏. Don't hesitate to tell me if you need any more help.

    Good luck! 💪

    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

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub