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

Blog preview card . it is not responsive

Rahul•50
@rahul11636
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


my project is a blog preview card created using HTML and CSS. It displays an image, title, description, and a "Read More" button, providing a snapshot of a blog post. This simple web component serves as a visual representation of blog content, demonstrating foundational skills in front-end web development. you should please screen 10% minmum decerease.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Davide•330
    @deedeedev
    Posted over 1 year ago

    Hi @rahul11636 , nice job. To improve the responsiveness of the card you might want to avoid setting a percent width on your container div and use a fixed width or a maximum width in px or rem. So instead of doing:

    .mini-container {
      width: 25vw;
    }
    

    you could try something like:

    .mini-container {
      max-width: 24rem;
      padding: 20px;
    }
    

    To fix the problem with the image you can remove the position: relative top and left rules and just apply width: 100%.

    The approach is this: use a container with a fixed width/max-width (that can change using media queries, depending on display size) then apply some padding on it and place your content inside. You might also want to look into flexbox, it really simplifies content aligning once you grasp how it works.

    Keep up the good work! 👍

    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