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

Insure Landing Page - SCSS, Grid, Flexbox, JS

sass/scss
Anna Leigh•5,135
@brasspetals
A solution to the Insure landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, everyone - it's been a few months! Getting more comfortable with Grid and still working on my Sass architecture. As always, please let me know if you see anything that can be improved upon. Feedback is greatly appreciated! 😄

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted over 4 years ago

    It's awesome to see you post another solution, Anna. Welcome back! 👋

    Your code looks great, scales up/down nicely, and it's awesome to see you using min-width media queries! The only suggestions I could find were in your HTML:

    • You've duplicated the navigation code when you don't need to. Instead of duplicating the HTML, you could style the nav differently for mobile or desktop layout inside a media query.
    • It's great to see you using a button element to trigger the mobile menu. If you want to take it up a notch and make it more accessible, I'd recommend checking out this Inclusive components article on menus & menu buttons. Add aria-* attributes will really enhance the accessibility of the navigation.
    • You've got 3x img elements with alt text of "illustration". These add no context to the content, so I'd recommend leaving the alt attributes blank, making screen readers skip them. As it is, screen readers would read out the word "illustration" before each of those 3 blocks, which doesn't add anything and actually makes the experience worse.

    I hope that helps. Let me know if you have any questions! 👍

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hello, Anna! 👋

    I'm so happy to see you submit another solution! 😆 (I was wondering when you'd come back!) 😉

    Excellent job, as always, of course. Everything looks good and responds nicely! I like the fade in/out transition you added to the mobile navigation. 🤩

    Your code looks clean and organized, too. 👍

    Well, keep coding (and happy coding), as always! 😁

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

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