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

Equalizer landing page

accessibility, bem, sass/scss
Galina McKoy•150
@GalinaM-G
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi! I would really appreciate if someone could help me with:

  1. I still find hard to understand a design file. Where is the correct position for the background decoration bg-pattern-1? Do I add it to body or .container?
  2. Is there an easy way to convert px to em or rem? I've just started using them.
  3. How to set an image correctly, so it would be perfectly responsive))?
  4. I applyed :hover on icons. How do I make the transition between colors smoother?
  5. What is the best way to make a responsive website? I've got an idea what to do, but when I need to match a website to a designer view of a responsive layout, I really struggle;)

Thank you a lot in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello Galina , congratulations for your new solution!

    ❓ Answering your question:

    1.If you're using VSCODE there is a plugin that allows you to convert automatically px to rem. The name is pixel to rem. Here's the link:

    https://marketplace.visualstudio.com/items?itemName=sainoba.px-to-rem

    Here's an online tool to convert: https://codebeautify.org/rem-to-px-converter

    2.Its better you add the background images ever in the bodyto make it stays underneath everything.

    3.A best practice to have all the image inside the container scaling and respecting the size of the container, you need to add max-width: 100% and add alsoobject-fit: cover to make the image auto-crop when resizing inside the column:

    img {
        display: block;
        object-fit: cover;
        max-width: 100%;
    }
    

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • Ndupu Adaeze•110
    @vermilion4
    Posted almost 3 years ago

    Hi Galina, nicely done👏... regarding your 4th question, you can add an ease-in-out, ease-in or ease-out to your transition as per your preference.

    5th question: it depends on you really, most times you find yourself using flexbox or grid depending on if the layout is 1D or 2D, other times you might end up using frameworks like bootstrap and not to leave out your media queries. It's more like using what feels right at the moment?

    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
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

Oops! 😬

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

Log in with GitHub