Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Blog Preview Card using CSS Flexbox

accessibility
Desmond Maina•90
@des254
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?

I wrote my first HTML/CSS with Flexbox and Iam really proud.

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

Centering a div. I read several articles but am looking forward to practicing more.

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

Specify width and height of a flex container.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vitaly•60
    @V0000DY
    Posted 4 months ago

    Great job on completing your HTML/CSS project with Flexbox! It’s awesome that you're proud of that.

    Here are some suggestions for their project:

    Centering a div can indeed be tricky, so don't worry too much about struggling with it. The fact that you read several articles to overcome this challenge shows your dedication to learning. Practice is key, and you'll find that with time, centering elements will become second nature.

    It's common to face challenges when specifying the width and height of a flex container. A good approach is to ensure that the parent container has a defined height or a min-height to properly contain its flex items. Also, explore the different properties like flex-grow, flex-shrink, and flex-basis to control how flex items behave within the container.

    If the sizes are off, double-check the dimensions specified in the project's design files against your CSS. Sometimes, a small discrepancy can throw off the entire layout. Using browser developer tools to inspect elements and compare their sizes against the design can be helpful.

    Keep experimenting with different values and observing how they affect the layout. There are also many resources available online, such as articles, tutorials, and interactive Flexbox playgrounds, that can help you deepen your understanding.

    Consider writing READMEs for your projects to explain your code and process to others.

    Your willingness to learn and overcome challenges is evident, and with continued practice, you'll become a proficient front-end developer. Keep up the great work!

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