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

Responsive Blog Preview using HTML and CSS

P
usman frontend 360•130
@Tech-Badhead
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?

First off i am proud of how i tackle the project heads on. Secondly, through this project i was able to learn a new css property which is the "clamp" property. what i would do differently next time would probably to be in the right frame of mind before taking the next challenge.

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

I had challenges structuring the web content. I was able to overcome it through persistence and many try by error.

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

I tried to reduce the avatar image size but to no avail. my subconcious mind kept telling maybe it was because it's in SVG format. i am open to correction tho!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ImagineBillie•120
    @ImagineBillie
    Posted 3 months ago

    Quick Code Review

    • Fonts & Design

      • Import the exact variable font that given in the folder
      • Figma files give you more details. worth check it out the spec and match its sizes/weights.
    • Avatar Fix
      You have typo id="autor-image" and CSS targets #author-image. Either rename the ID or switch to:

      .author-profile img {
        width: 32px;
        margin-right: 12px;
      }
      

    Responsive Layout

    .container {
      min-height: 100vh;
      padding: 3rem 1rem;
    }
    .card {
      width: 90vw;
      max-width: 340px;
    }
    

    CSS Cleanup & Best Practices

    • Consolidate your reset into one * { box-sizing: border-box; margin: 0; padding: 0; }.
    • Prefer classes for styling over IDs.
    • Use rem or % units for font‑sizes, margins, and paddings to keep everything scalable.
    • Leverage your clamp() on html { font-size: clamp(14px, 1vw, 24px); } and build all text using rem so the whole UI scales smoothly.
    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

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