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

Equalizer landing page, flex.

Nazemrap•200
@Nazemrap
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Got some trouble at first, had to delete my first version and rebuild it from scratch.

  • difficulties to organize my self for the media query. Looks like i did it upside down. I should have start with the simplicity layout and go toward the more complex one. (From the phone to the bigger screen for that exercise.)
  • Also, I should get away from the px - i should use more responsive unites measure. But how should i use better Rem or vh, i understand what they do but i don't get, yet, how to use it properly especially for an exercise like that.
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jannie Hansen•110
    @Jawha3
    Posted over 3 years ago

    Hey Nazemrap - great work getting it done despite the struggles.

    I've recently learned myself to definitely use the mobile-first approach as it makes everything so much easier and you will end up with less redundant work.

    In terms of using rem, vh, vw - I personally use rem a lot especially for elements that are crucial such as font-size, margins and paddings. I am still learning to use vh and vw properly but from what I understand a vw length is relative to the full width of the browser window and of course a vh would then be the full height of the browser window.

    So if you used vw for font-size you could use calc() so the font-size doesn't scale drastically and becomes super small and unreadable. I reccomend checking this out: https://css-tricks.com/fun-viewport-units/ to learn more about it.

    I hope that shines some light on your difficulties. :)

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Greetings, Nazemrap! 👋 Good effort on this challenge! 👍

    Regarding your questions.

    • I would recommend writing the styling with the mobile-first approach. It often leads to shorter and better performance code. Also, mobile users won't be required to process all of the desktop styles.
    • Like @Jawha3 said to you, the rem unit is going to be the main unit in the stylesheet. There's also em unit which is relatives to the font-size of the parent element. All things that commonly use px can be converted into rem units. I only use vh unit for the card component challenges, usually to make the card in the center vertically while using flexbox.

    Some feedback.

    • I notice that there are some font-family properties in the stylesheet. I would recommend putting the same styling once for the same elements. It's going to prevent you from writing the same styling. Even better, since this site only uses one font family, you can put the font-family property on the body element. Most elements inherit the styling from the body element so you don't have to keep specifying the font family for each element.
    h1,
    h2 {
      font-family: 'IBM Plex Sans', sans-serif;
    }
    
    • header element should only contain the logo and the nav element.
    • The alternative text for the logo should be the name of the company which in this case, Equalizer. Alternative text for images should not contain any words that related to image (e.g. picture, photo, logo, icon, graphic, avatar, etc). It's already an image element so the screen reader will pronounce it as an image.
    • Not all images need alternative text. In this case, all the illustrations and social media icons are decorative which means that you can leave the alt empty. By doing this, you prevent the screen reader users from listening to unrelated content. For the illustrations, you can make them as background images or pseudo-elements if you want.
    • Use interactive elements (a) for the download buttons.

    That's it! I hope this information is useful! 😁

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub