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

Blog preview card with responsive font size using clamp()

sofiasmnk•110
@sofiasmnk
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 challenge said to make the text responsive without using media queries. It wasn't hard to find guides online on how to do that with clamp(), though figuring out the vw width value that seemed to work best was a bit trial and error. I'm glad the card width being responsive also worked without media queries.

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

There were some inconsistencies in the Figma file. The "Design System" page claims spacing-200 is 16px, but the variable in Figma itself is actually set to 24px. It took me a while to realize why the padding on my version looked smaller than the one on Figma and on the preview file. In the end I decided to set it to 24px to follow how it looked rather than what it said.

I also noticed that in the mobile version, the author's name is the only piece of text that doesn't get smaller. It felt weird to set a different font-size just for the author name that wasn't the responsive custom property with clamp(). So instead, I let the author name be resized as well, and just set the author image size in em instead of rem so that it would be sized down along with the text and not look weird.

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

On Safari, the SVG image has this weird bug (?). The "{" shapes on the bottom right corner are supposed to be half-black and half-white – when I open the page in Safari, they look all white. Weirdly enough, if I click and drag the image, it switches to showing half/half properly, but if I refresh the page it's all white again. I was afraid my CSS was affecting the image's styles somehow, but after checking, I saw all the SVG's colors are hard coded in hex code inline, so I don't think that's possible? I saw it seemed to be working fine on Firefox, so I chalked it up to Safari and gave up on trying to fix it, but it would be nice to know what's going on...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • joyafrikaana•70
    @joyafrikaana
    Posted 10 months ago

    Your code is well structured and readable. I love that it includes semantic HTML

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