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

Equalizer Landing Page | HTML CSS Sass

accessibility, bem, sass/scss, lighthouse
Vanza Setia•27,715
@vanzasetia
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Everyone! 👋

This was, in my opinion, the hardest newbie challenge. There were a lot of decorative images that I needed to take care of. I even ended up doing a revert commit to rewrite the styling. However, It's a nice and fun challenge that really tested my CSS skill, and I'm glad I was able to complete it. 😊

I don't have any questions. However, feel free to give me any feedback or comments. 😉

If you have finished this challenge and would like me to give feedback on it, please include a link to your solution. I would be glad to help you! 😀

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Angelo Barbarulo•280
    @Jorahhh
    Posted over 3 years ago

    Wow Vanza, it seems as perfect as the original! Love the responsiveness here.

    By the way, some days ago I did this challenge too, and I have few "issues" to which I have not yet received an answer.

    Hope you can take a look: My challenge

    For a beginner like me would be great to have some feedback from someone more experienced.

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

    Hey Vanza - it looks really great!

    I'm nowhere as experienced as you and would love to get your feedback on my own solution - https://www.frontendmentor.io/solutions/equalizer-landing-page-GVb4iQ1bL

  • Hamzat Lawal•560
    @EngineerHamziey
    Posted about 3 years ago

    Hi Vanza your work is great and you're such an amazing person for giving such an helpful informative feedback on people's work. I have been reading alot of your comments on other people's work and they are all amazing. I would very much like you to help review my challenge

    Thanks alot for being helpful to everyone 😊

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

Oops! 😬

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

Log in with GitHub