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

My first solution using CSS

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

Solution retrospective


My first difficulty in this challenge was in the process of deducing the sizes of the elements on the screen and I “wasted” a lot of time with that, so I'd like to know some tips on how I can make this design process a little faster.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dipesh•430
    @Dipesh-sapkota1
    Posted over 1 year ago

    Hi @Mjornog 👏 Congratulation for completing front-end mentor challenge.🎉

    • To answer your question for how to dynamically change size of an element? I would like to say It is not necessary to add height and width to a div. Naturally, browser tend to make web responsive, everything will fall into its place own its own and make necessary changes when it is required. We make web unresponsive by adding extra properties.
    • You can implement these points to improve your code.
    1. Follow DRY (Don't Repeat Yourself) principle

      • I saw too many repetition of same properties, use CSS variables to define properties at one place and you can use it again for multiple selectors.
      • Learn about inheritance that will save you many lines of code.
      • Start your CSS with a good CSS reset and base CSS for your elements.
    2. Make your website responsive

    • You can start making your website responsive by following mobile first approach. It will make your life a lot easier.
    • Use CSS Grid or flex-box to make precise alignment of layout.

    3 . Organize your file structure

    • For small project like this does not require multiple CSS. If it requires to add multiple CSS then organize your files in separate folders.

    You did great on your project and happy coding! 👏🎉🙂

    Marked as helpful
  • Durga Jaiswal•230
    @Durga-Jaiswal
    Posted almost 2 years ago

    Put max-height : 100vh to avoid scrolling the page. It will help in making page do not scroll. Other than this all things are perfect.

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