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

Insure landing page with HTML & CSS only

Bethany•855
@whimsicurl-creations
A solution to the Insure landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project took a bit longer and it's certainly far from being pixel perfect, but I definitely learned quite a bit through the process. The part that is still bothering me a bit is the top section of the website (after the nav bar - the "Humanizing your insurance" part). The proportions and spacing are a bit off, but I wanted it to scale well. Recommendations on how to code that section more efficiently (and to better match the design) would be appreciated.

Thanks for taking a look!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Fins•145
    @clockwerkz
    Posted over 5 years ago

    Looking good! The headline looks more condensed in yours vs the design; I think maybe adding 1px of letter spacing might help that.. or maybe it's the font weight? Also, in the mobile version it looks like the page is still using the desktop version of the hero image... I would recommend using srcset to switch from the desktop to the mobile version of the image.. Nice work!

  • Lizz Rennie•195
    @LizzSoup
    Posted over 5 years ago

    Hello, fellow skillcrusher.

    Good work, and nice to see you on here! Hopefully someone can come through with the tips you're looking for.

    I've found it really difficult to get things looking pixel perfect without the sketch files, though there are some chrome plug ins you could look into the might help you get it a little closer.

    There's a very pale grey footer background that's missing on your version, should be an easy fix!

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