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

Equalizer Responsive Landing Page

Angelo Barbarulo•280
@Jorahhh
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Really nice and funny challenge!

I tried to make this landing page super responsive on almost the most (common) screen. But I'm not sure of what I've done. SO!

  • I did maybe too many '@media screen', but I'm sure there is another (and right) way to make it responsive as well, without using tons of lines code.

  • Had some problem with the orange square (in my code '.info'). I was undecided if I should use 'position: absolute;' or 'position: relative;'. By the way, I think that was not the better choice.

That's all, people! I would be glad if anyone would leave some feedback (or suggestion), specially on the first point.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted about 3 years ago

    Hey Angelo! Excellent work on this challenge! It's great that you've made such an effort on the responsive side. You have quite a few instances where you're setting specific heights, widths, margins, and other values to position elements. This seems to be what's contributing to most of your repetitive code.

    I'd recommend checking out Every Layout, which is an excellent resource to help shift layout decisions onto the browser instead of manually overriding your own code and fixing positions.

    If you find yourself writing code like margin-left: 13%; and top: -410px;, it's usually a sign that there's a better way to do it. These are what developers call "magic numbers" as they're pretty arbitrary and are essentially plucked from thin air.

    You'll find yourself using them less and less as you continue to gain experience building projects. So, for now, it's mostly a case of being aware of it and then trying to find more reusable solutions whenever it happens again.

    I hope this helps! 🙂

    P.S. Please try to avoid swearing in your messages as it goes against our community guidelines. You can edit your message by going to "Visit challenge hub" at the top of this page and updating your solution. Thanks! 👍

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

    Hello, Angelo! 👋

    Thank you for taking the time to see my solution! I appreciate it! 🙌

    Anyway, good effort on this challenge! 👍 It's great that you used the mobile-first approach when writing the styling! Well done! 👏

    Regarding your questions.

    • About the responsiveness of this project, I would rather set a .container that limits the layout to 1440px and then have a margin: 0 auto to make the content in the middle of the page on a larger screen. That way, you don't need to worry about bigger screen sizes. Also, it's worth knowing that usually, people that have a large screen will have zoom level around 150% to see the website.
    • I used relative positioning on mobile layout and for the rest of the layout, I used absolute positioning for the card element or in this case, the .info element. I would not recommend setting a height and a width on the card element. Most of the time you want to let the element inside it dictate the height of the parent element and use max-width instead. It's worth doing because in reality, the content of the page might change so it might be harder to maintain if the content change often (keep adjusting the height).

    Some more suggestions.

    • Reduce the amount of whitespace at the bottom of the page. Currently, there's so much whitespace in the footer.
    • Use either rem or em for the margin instead of using %. By using %, the margin might result in unexpected behavior on some screen sizes since it always depends on something. Also, unlike width where you can set a max-width to limit the amount of width, margin on the other hand doesn't have it.
    • The download buttons should be link elements with download attribute. button elements.

    I hope this helps! Keep up the good work! 👍

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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