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

Responsive blog-preview-card

Pritam Panda•60
@imxeon
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?

The design looks pretty similar. I would understand and apply responsive design in a better way next time.

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

This design looked simple and is simple. But it took more time to build it

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

I need feedback on making this layout responsive so that It retains this aspect ratio on any screen.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • gfunk77•1,270
    @gfunk77
    Posted about 1 year ago

    Nice job on your solution. The card looks really nice. I would suggest a few things that might help:

    • You have many 'containers'. For example, you can remove the id="rounded-box-section" entirely and just put those styles on main.
    • .rounded-box might make more sense being labeled as .card.
    • try to avoid using fixed width and heights on elements. That removes responsiveness. So for your .rounded-box, try something like width: 90%, max-width: 345px. Let the elements inside control the height, no need to set it.
    • You don't need a div for both category and publish-date. Put both the h5 and p inside one div.
    • Same for heading and description, they can both go inside one div

    I think you did a great job on the card. I hope this feedback is helpful to you.

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