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

HTML, SCSS, JS - Mobile First

Amon•2,560
@A-amon
A solution to the Insure landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Its my second try at mobile-first. My thoughts on mobile-first method is that it feels like it makes the coding a lil less complicated (I might be wrong tho!)

Anyway, any feedback and suggestion is welcomed!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anna Leigh•5,135
    @brasspetals
    Posted about 4 years ago

    Hi, Amon! Congrats on completing this challenge! 🎉 I definitely think mobile-first makes coding easier, and typically also makes the transitions between layouts looks smoother. 👍

    Overall, good job on this one! You followed the design nicely, and I noticed you made some nice changes and tweaks since your initial screenshot. I know that hero image was tricky!

    I do have a few suggestions:

    • Your nav__button text gets lost when hovered on desktop. Although unlikely to happen on mobile due to touchscreens, the hover states for all your mobile nav links also get lost on hover as they’re the same purple as the background.
    • You may also want to consider adding some max-widths to your paragraph tags. The ones on both the hero and the differences section get stretched out before hitting your tablet styles, as well as on large screens (1920px).
    • Speaking of large screens, you might want to take a look at the hero section in particular and see if you can make some adjustments to stop the image from overflowing and covering up some of the “differences” section text.
    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