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

Responsive Blog Preview Card using Flexbox

P
Aakash Dasgupta•360
@a-d14
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 am proud of how responsive I made the project in the first try this time.

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

One thing I could not figure out is how I can send the footer to the bottom of the page. Would appreciate some help with that.

One thing I noticed is when I set the height of the image as per the figma specifications, the border-radius disappears. It reappears when I set object-fit to cover. Would love an explanation as to why that is happening.

I had an issue with maintaining all the different font types and their sizes and would often get confused. How can I better deal with fonts?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bhuvnesh Upadhayay•2,120
    @bhuvi819381
    Posted 5 months ago

    Hey brother,

    Your solution looks great! 🚀

    Here are a few suggestions for improvement:

    1. 🔠 Use One <h1> Per Page

    Each page should have only one <h1> tag for proper structure.

    1. 📏 Follow Heading Hierarchy

    Use headings in order: <h1> → <h2> → <h3> instead of skipping levels.

    1. 📐 Avoid Fixed Height

    Instead of height: 500px;, use min-height or flexible layouts to ensure responsiveness.

    1. 📱 Reduce Media Queries

    You don’t need a media query for this specific case. Avoid excessive media queries; use flexible units like rem, %, or flexbox instead.


    Additional Suggestions:

    🛠️ Check for Errors: After submitting the solution, always review the HTML and accessibility error report. If you find errors, resolve them.

    Keep up the great work! 💪

    Marked as helpful
  • ChrisTariah•80
    @ChrisTariah
    Posted 5 months ago

    what are the different ways to align every element on the page,to achieve the layout.

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 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