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

Equalizer Landing Page using CSS Grid, Flexbox and CUBE CSS

accessibility, cube-css
Jordan•140
@joanFaseDev
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


First and foremost, english isn't my first language so please forgive me for any mispellings or grammatical errors.

I had a lot of difficulties on that project.

Part of it was about using CUBE CSS methodology when i have no idea what i'm doing half of the time. My naming convention for class utilities need serious reworking because near the end of that project i had troubles remembering some variable's purpose. The fact that i mixed up some BEM conventions as well only did it worse so in the future i'll be sure to use simple naming conventions which can carry me through from start to end.

Another problem, the biggest really, is how to transition smoothly between different designs (mobile, tablet, desktop). Replicating each individually is one thing and i'm confident i can do it BUT transitionning from one design to the other without it being awkard is totally different and unfortunately i can't seem to manage it without excess use of absolute length units which aren't great at responsive design. And event then, the end result is less than average. If anyone had advices concerning any of theses two problems, i'll gladly accept them.

That being said, that project was a huge opportunity to learn and even if the result is far from great i'm glad i saw it to the end.

Thanks for reading, have a nice day and happy coding to all :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jordan'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.