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

Responsive landing page. Tried to make it pixel perfect

Éric Férole•420
@Eric-Ferole
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What I learn :

  • Fixing the differences between breaking point were fastidious but helped me to read better the style tab in the devtool.
  • CSS files can become very long and even naming our selector correctly, it can be tough finding things.
  • To avoid Float properties.
  • How to manage within the Chrome screen resolution tab.
  • Pixel perfect is not the good mindset to have as a designer.

I Never thought I would say that but coding for pixel perfect is extremely time consuming and I question the benefits for the user.

Searching for media query on how to target different browser size, I stumble on a Stackoverflow answer that took my attention. The user Dave Everitt suggest to avoid targeting specific devices or sizes. But rather doing the following :

  • develop the site for mobile first using percentages or ems, not pixels,
  • then try it in a larger viewport and note where it begins to fail,
  • redesign the layout and add a CSS media query just to handle the broken parts,
  • repeat the process until you reach the next breakpoint.

As a designer I like to know that my design will be seen as I designed it. But in the end, what for ? Isn't it better to give the user the best possible experience no matter what screen they are using? Let's get it right, I'm not saying design and precision are not important, I'm just saying we should just put the user's best interests first. The purpose of our design isn’t to help the users to achieve their goals ?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kamasah-Dickson•5,570
    @Kamasah-Dickson
    Posted over 3 years ago

    I really like all what you shared in the "community question" I think what you shared will be really helpful to me. Like the use of em units for media breakpoints

    Also your design looks great...its pixel perfect I will say:)

  • Mojtaba Mosavi•3,740
    @MojtabaMosavi
    Posted over 3 years ago

    Congrats on learning a bunch of useful insights and taking the time to reflect, here are some sggustion that came to mind reading you reflection.

    1-Learning about BEM is great way to midigate the issue with naming, specificity, reusability and structure.

    2- BEM works incredably well in conjunction with a 7-1 architeture which helps you take a modular approach to writing styles and breaking them down into logical chuncks that once put togather in a main file build the UI, it's like playing lego, the lego parts being your logic chuncks and once you put them togather you've the UI.

    Regarding you toughts about pixel perfect solution being time consuming, my rule thumb when for this is that often time a accuracy rate of 80-90% is enough but sometimes you've to weigh in if it's worth it to for 100%.

    Keep coding :=)

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.

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