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

Insure landing page - HTML, CSS and a little JS for the burger menu

P
Dave•5,295
@dwhenson
A solution to the Insure landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I wanted to work on a hamburger menu component that I could use again in other projects I think this one based on Andy Bell's tutorial works well.

I found the top section very difficult to get right (the breakpoint is still not 100% good) especially working with the image. I will try another challenge focusing on images. Any advice on how this could be done better or resources for learning about working with images in layout would be appreciated.

Any other feedback on any points would also be most welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hello there, Dave! 👋

    Good work on this challenge! 👍 You've done a nice job, as usual, (everything looks pretty good and responds rather well)—and I like the spinning animation you added to the mobile menu icon (just add something like overflow: hidden to the body when the navigation is toggled)! 😀

    A few things I'd like to suggest are,

    • Increasing the size of the text of the navigation links in the footer of the page in the desktop layout (they are quite small, at the moment).
    • Adding overflow-x: hidden to the body to get rid of a horizontal scroll bar that is showing up along the bottom of the screen in the desktop layout.
    • Typically, vertical scrolling is disabled when the mobile navigation is toggled so that users can just focus on the options they have available to them (and I think things feel a little out of place if you are able to scroll down since now part of the page is covered by the menu and you to disable it anyway in order to access the rest of the content on the page). As long as there is a clear way to disable the mobile menu (so that users can easily exit out of it), I think disabling vertical scrolling when the mobile navigation is toggled would be a nice idea! 😉

    Of course, keep coding (and happy coding, too)! 😁

  • Uzochukwu Okafor•355
    @uzoway
    Posted over 4 years ago

    I just posted screenshots of what I mean

  • Uzochukwu Okafor•355
    @uzoway
    Posted over 4 years ago

    Hello Dave! I just visited the site(on mobile) and I must say you did well. Although, there's something I'd like to point out. On the mobile layout, the hamburger and Mobile navigation page is only accessible on the first page. I think it should be fixed(position) so that at any point on the page, one can easily navigate the site.

    I'm actually working on this challenge and you just motivated me to finish it😄

  • Uzochukwu Okafor•355
    @uzoway
    Posted over 4 years ago

    On the slack channel

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.

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

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