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

Responsive blog preview card using flexbox and clamp() functions

P
Alexander3717•310
@Alexander3717
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 like how I managed the text responsiveness without media queries by using the clamp() functions. However, I set their parameters based on calculations I made on the side so they look like arbitrary values. Maybe next time I should find a way to do them directly in the stylesheet but that seemed too complex for the size of this project.

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

The clamp() function takes a min, max and 'preffered' size of text which you can specify in a relative unit like vw. Problem was, the blog card reaches its maximum size quite quickly and after that point even if screen keeps getting bigger, the card stays the same. But because text size is in vw, the text in the card keeps growing. And in this case, we don’t want that – we want the text size to be dependent only on size of the card, not on screen size. I solved this by calculating on which screen width the card reaches its maximum size and set that as max viewport width in https://utopia.fyi/clamp/calculator for each text preset (min I set to 375px, the width of the mobile design in the figma file)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • pabjunior•40
    @pabjunior
    Posted 4 months ago

    Great job on the project!

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