Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Results summary component | How to properly scale? | Variables ?

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

Solution retrospective


Hello everyone! No major difficulty in recreating this page, but I have a recurring issue that I would like to solve. How do I properly adjust the size of the HTML? In the example, the mobile version was supposed to take up the entire page, and the desktop version was supposed to be centered. However, it seems like the size of my HTML file is limited. I think the solution is simple, but I prefer to ask!

Another concern, I'm a bit confused about the use of h1, h2, h3. Is it based on the importance of keywords on the page? Is it okay if they are out of order in the page chronology? (e.g., h1 > h4 > h2)

And one last question, when I wanted to change the color of the "reaction" block for example, I was looking for a way to take the variable used to color the text and just reduce the alpha of that variable for the background color. However, I can't figure it out. Any solutions? Thanks in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roraima Lugo González•510
    @roraima1986
    Posted over 1 year ago

    Hello, you could use flexbox inside your .main to centralize

    main {
          display: flex;
          justify-content: center;
          align-items: center;
     }        
    

    It has worked for me when I want the design to be completely centralized on the page.

    With your question about the headings from h1 to h6, if the order is important. They are used to define the titles and subtitles of a page. In addition, they are a powerful SEO (Search Engine Optimization) tool since, thanks to these HTML headers, we can provide hierarchy to the information and tell search engines what the content of our website is about.

    Follow these best practices and optimize the use of HTML header tags in your code:

    • Avoid skipping HTML header levels. That is, always start with <h1>, then use <h2> and so on.
    • Avoid using <h1> more than once on a page. This tag is used once to display the page title, followed by the other HTML headers, starting with <h2>.
    • You should also not use lower levels to reduce the font size. To do this, apply the CSS font-size property.
    Marked as helpful
  • Dêvid Teófilo•240
    @devid8642
    Posted over 1 year ago

    Firstly congratulations on the solution, I just have a small tip in relation to what has already been said:

    To center the card, in addition to using a flex display as already mentioned, consider also using: height: 100vh; to completely center;

    Marked as helpful
  • Dêvid Teófilo•240
    @devid8642
    Posted over 1 year ago

    Hello, I'm here again. I was also wondering if there was any way to use color variables in the way you described. Fortunately I found this css resource: https://www.w3.org/TR/css-color-5/#relative-colors. I believe it serves our case well.

    Here is an interesting explanation of this new syntax: https://developer.chrome.com/blog/css-relative-color-syntax/.

    However, as this is a new feature, it is not yet supported by all browsers (currently when I write this comment, the most recent version of Firefox does not support this feature, for example).

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