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

CSS flexbox put to use

Tee12thegreat•80
@Tee12thegreat
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?

how i could relate to my codeeasily and applying the things i learnt in the previous challenge

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

i could not put shadows on my container. i lso couldnt align an object to the left. i managed to browse through the internet and get solutions

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

aligning objects

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Atef•50
    @AhmedAtef32
    Posted 9 months ago

    You did it well. My advice to you is not to use width as px and not to use text center in the container. And use semantic tags to make performance better.

  • Wisdom•230
    @Unifies
    Posted 9 months ago

    Hi again, I promise I'm not stalking you lol - I just keep getting your solutions for peer review in this learning path.

    Nice work completing the project!

    Some feedback for you:-

    The alignment on your solution is off, it looks greatly different from the design. The content is supposed to align to the left, not center.

    There's an extra padding in the "Learning"'s padding - include display: flex; to the "box" div containing Learning and see if that works correcting the extra padding

    Tip: This challenge comes with a free Figma Design File and it greatly helps in getting the correct values for the widths, spaces, font sizes, font weights, border radius [practically every info you'll need to match the design exactly] and it fastens the coding process as there's less guess work or trial and errors.

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

Oops! 😬

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

Log in with GitHub