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

Fluid Sizing, Minimal Media Queries Using CSS Clamp(), calc(), vw unit

John Rey Faciolan•220
@juani2
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is the first version of my solution and I'm actually working on another version of this solution in SASS. This is just an initial solution.

In this challenge, I was able to find a not-so-elegant way of calculating responsive margin which grows inversely proportional to the viewport width.

I achieved this by plotting the viewport(x-axis), and length(y-axis) into a cartesian coordinate plane a do a little bit of math using the two-point form equation of a line.

In summary, I was able to create a preferred value for clamp() function that goes like this: f(x) = m(x - x_2) + y_2 or current_length = (slope)(current_viewport - max_viewport) + length_at_max-viewport.

Example usage of this function is the margin-bottom of my navigation bar: at 375px viewport width, its margin-bottom should be 80px but on 1440px viewport width it should be 71px. That is margin bottom grows inversely proportional with viewport width.

My code in this solution was not so clean and I'm currently re-implementing it using sass so that they are friendlier to read.

Also, my footer section was not very the same as the design since most of my energy was focused on the responsive sizing thing but I just want to share my current progress for feedbacks.

I would be very happy to hear feedback from you guys to improve the next iteration of my solution.

Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    well it seems to be really good but you should check your H1 around 1300px to 700px it does not seem centered

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