Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive landing page using float - result summary component

web-components
codewthv•60
@codewthv
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm glad that I was able to complete this project and I've been able to learn a lot from this project to complete this project. I decided to try using Float in this project although I could use Flexbox or CSS grid. I just wanted to try something new and I guess it worked perfectly. Next time, I would try using flexbox and CSS grid since I've learnt it better now.

What challenges did you encounter, and how did you overcome them?

Initially, I tried using Flexbox cause I just started learning about it but it got kinda messy and I had to look for alternatives. Later on, I learnt about CSS grid and Float and I decided to use Float for this project and it worked!!

What specific areas of your project would you like help with?

I would like to try out using frameworks to build this project. And I'm still trying to learn how to use linear gradient and CSS colors generally.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • jabo Landry•250
    @jabo-arnold-landry
    Posted about 1 month ago

    I would recommend you to first understand the layout design using flex box and grids because float was used in previous years before flex and grid and it was used to make layout and then they introduced flex box and grids to help make a more responsive and good looking layout so float is not recommended to use it for layout even though it is still being applied.

    And the reason for this is that flex and grid provide more tools and ways to make responsive layout without using media queries or container queries which float can't, My advice to you would be to first understand those two layout concept and then jump to framework because flex and grid are now the most used building blocks to build layout.

    And you did a great job continue with the flow you will get there.

    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, SASS, 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