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

Suite landing page

sass/scss
Christian Palacios•360
@codepalacios
A solution to the Suite landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, media queries are a bit difficult for me and I would really appreciate advice on best practices on this or alternatives to better ways to use them in this project for a better user experience.

Regards :D

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ivan Netreba•210
    @ivannetreba
    Posted almost 2 years ago

    Wow so close to design! Very good! You use many nestings. Can it make maintaining code more harder?

    Marked as helpful
  • P
    Alexandra•580
    @Alexandra2888
    Posted almost 2 years ago

    Hi! Congrats for finishing challenge! Your solution is very close to the design! In general it's better to start coding for mobile first (that means 0-767px) after increase for tablet (min-width:768px) and after that for desktops (width for desktop in general is provided by the design, can be 1024px, 1200px etc). Don't try to keep everything "in place", you can't predict where every px will stay on a user's screen. As Kevin Powell says "px perfect website doesn't exist". A user can see your page from a Nokia 3310, another from a 50 inch screen and another will navigate your site using a screen reader so you can only predict how everything will look. Happy coding and don't stress :D

    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