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

results summary component using flexbox

Fayeโ€ข80
@FayeVinyl
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was unable to figure out how to add the corner borders to the summary section. I'm certain my css could be cleaner. I learned a lot about flexbox

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq ๐Ÿš€โ€ข72,380
    @0xabdulkhaliq
    Posted about 2 years ago

    Hello there ๐Ÿ‘‹. Congratulations on successfully completing the challenge! ๐ŸŽ‰

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    POINTING CURSOR โ†—๏ธ:

    • Looks like the component's button element has not a pointer, this property plays a major-role in terms of both UI & UX

    • The cursor: pointer CSS property is important for button-like elements because it changes the cursor from the default arrow to a pointer when hovering over the element. This provides a visual cue to the user that the element is clickable and encourages interaction.

    • In terms of UI/UX, using cursor: pointer helps to improve the usability of the interface by making it easier for users to identify interactive elements. It also helps to provide feedback to the user by indicating which elements are clickable and which are not.

    • So we want to add this property to the following button element
    button {
    cursor: pointer;
    }
    
    • Now your component's button has got the pointer & you learned about this property as well

    .

    I hope you find this helpful ๐Ÿ˜„ Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • _nehal๐Ÿ’Žโ€ข6,710
    @NehalSahu8055
    Posted about 2 years ago

    Hello Coder ๐Ÿ‘‹.

    Congratulations on successfully completing the challenge! ๐ŸŽ‰

    Few suggestions regarding design.

    • Use gradient button:hover

    • background-image: linear-gradient(#6542FE,#342CE2);

    • To properly center the container.

    • USING FLEXBOX

    body{
    min-height: 100vh;
    display: flex;
    align-items: center;
    justify-content: center;
    }
    
    • USING GRID
    body{
    min-height: 100vh;
    display: grid;
    place-items: center;
    }
    
    • For image like .svg are decorative which screen reader will not render it to be important and skip it, so it make no sense to add alt leave it blank.

    • Use cursor:pointer for buttons for more user friendly.

    • Use Semantics for the proper design of your code.

    <body>
    <header>
    <nav>...</nav>
    </header>
    <main>...</main>
    <footer>...</footer>
    </body>
    

    I hope you find this helpful.

    Happy coding๐Ÿ˜„

    Marked as helpful
  • P
    John Mirageโ€ข1,590
    @john-mirage
    Posted about 2 years ago

    hello,

    The corner border ??? you mean the shadow ?? if so this is the box-shadow css property.

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

Oops! ๐Ÿ˜ฌ

You need to be logged in before you can do that.

Log in with GitHub