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

Results Summary Component

Pauullamm•20
@Pauullamm
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Not sure how to position the attribution div such that it does not overlap with the result summary when the window changes size...

I also feel like my use of divs may have been excessive, as it's starting to feel a bit messy with all the different class names

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Henrique•200
    @devriquesant
    Posted about 2 years ago

    Hello pauullamm

    Congratulations for completing this challenge!!

    ✏️ Here are some tips and suggestions for this and your future projects ;) ✏️

    1. 🚀 Contain your "main" content in a "main" tag:

    • <div> do is a joker element and can be to a general container, but it does not provide, alone, a semantic value.
    • <main> is a semantic element from HTML which provides accessibility and organization for your web page;
    • Semantic elements provides detailed info about the contents in your page.
    • Others semantic elements includes: <header>, <footer>, <figure>, <figcaption> ...
    • To implement this, you should exchange the <div class="outerouterContainer"> for <main> and wrap all the necessary and main content of your page.

    1.1. ✅ Use the right attributes:

    • I noticed you used fixed position attribute to keep the contents in your page.

    • position: fixed; maintains the element fixed in a certain position of the page and it won't move.

    • 🧪 As a experiment you should try putting the body height with 100000px and see what happens as you scroll down 🧪

    • As your content is right there on the screen and it's needed to be responsive with the screen, position is not necessary to be set, but you can adjust with the display property and the values you give to them.

    2. 📱 Build a responsive web page:

    • Use px unit to dimension your components in the page gives it a appearance of static.
    • To build a more responsive one, you should start to use relative length units to adequate the page components to a device screen.
    • To deeper details, take a look at it

    ❓ THE PROBLEM ❓

    • The div.attribution element won't fit the right and will be still overlaping the main content if it doesn't have a container to set it in the right place.
    • This can be done by using <footer> element and extend it to the screen width and set the div.attribution in the center. (It is just a pobbile solution) :)

    Overall you did great with this project, keep coding! I'm sure you will discover new things and become even better

    Here, take a star for achieving it: 🌟 <- it's a glowing star if you're seeing a rectangle :)

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub