Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Flexbox and fluid typography with CSS clamp() and viewport units

Riley•260
@rileydevdzn
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys!

Playing with fluid typography using viewport units and CSS clamp() function on this project. Also using Flexbox with minimal media queries. Intentionally not pixel-perfect, I wanted to compare how close the ‘fluid’ approach came to the design. Currently applying clamp() on individual elements, but declaring global variables under root in a similar approach (t-shirt sizing) is on my list for a future build.

Any suggestions/feedback always welcome, and thoughts on my implementation of CSS clamp() would be greatly appreciated! I focused on font sizes, but I’ve also applied to some widths, margin/padding, and a row-gap in there with it to experiment with what all I could do with it now that I’m getting the hang of the calcs. I went with a formula for the preferred (middle) variable instead of a single value.

A couple of questions:

  • Math(s) question: how much precision do you apply in your function variables? Two decimal places? Three? Four? Wondering what the best practice is here.
  • I used em units for line heights (based on the design), though I realize this is a bit simplistic. I’ve also seen clamp() used for line height in relation to text length (longer width text with more line spacing, and vice versa). More of a design question, but curious what anyone else has seen or used? Any method you preferred or found worked better?
  • And finally, buttons vs. links! I used a link for “Proceed to Payment,” seemed to me it was intended to take the user to a new screen instead of submitting data to the server. Styled to look like a button to match the design. If it was on a full page, and if it generated a pop-up/modal I could perhaps also see an argument for button (type=button)? What do you guys think?

Thanks!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Riley's solution.

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.