Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

Responsive webpage using flexbox

Matteo Lipošćak•10
@plebku
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 am proud of how I easily setup the html part and then aligned everything up until very end where I encountered an issue of specific aligns that I did a sloppy fix with margins and using widths.

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

I had issues with perfectly aligning elements, I did a sloppy job of overcoming some of them with margins and width.

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

On how to perfectly align everything without having to using margins/width fix.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Evans Macharia Kabubii•170
    @EvansKabubii
    Posted about 2 months ago

    Hi, one thing you could have an easy fix for here is:

    1. I notice your page is scrollable. You can stop this by setting the body height to 100vh, and applying box-sizing: border box; to everything. This will instantly, and easily make your page cleaner.

    2. On aligning things, play around with displays. Personally, whenever centering, I'm super biased to just apply display: flex; then using the justify-content: center; and align-items: center; to get everything centered horizontally and vertically. Avoiding margins and stuff like that may be a difficult ask, but it is possible.

    Good job, good luck

  • VeyronShark•130
    @VeyronShark
    Posted about 2 months ago

    It's great work dude. regarding your question about accuracy with precision, I noticed a lack of the usage of padding. Padding is my all saviour when it comes to spacing inside flexboxes, grids etc. I think you should try using padding most often and only using margin, or spaces that are not used anywhere else. For eg, the 4 summary types all have equal space on their left and right. so instead of using margin-left, you can make the whole .summary-container as a flexbox and give it some padding on the left and right (even top and bottom since the "Summary" heading and the "Continue" button also have space between them and the border)

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