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

Results Summary Component

angular
Samuel Larbi Danquah•30
@outHereSam
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?

This project helped me apply some data fetching techniques using json-server and services in Angular. I was also able to apply some component architecture knowledge learnt from the previous material by breaking down the design into components. I would definitely build the designs from mobile first going forward.

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

It wasn't really a challenge but I was able to implement a much simpler way of fetching data using services and asynchronous data fetching techniques.

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

For designs like these, should I go with pixel perfect applications, in the sense that if the design file says a card has a width of 200px, should I hard code the card to have the exact width? The reason I ask this is because, the part of the design where the actual summary goes, I didn't hard code the width of each category card but instead used flex gap to give the spacing between the category title and the score.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 12 months ago

    Hi @outHereSam,

    If you want to achieve a responsive design that looks as close to your intended layout as possible, you should replace fixed widths with min-width and adopt a mobile-first approach. Use media queries along with flexbox or grid to adjust the design for desktop views.

    Here are some best practices for responsive design:

    Avoid Using Pixels: Instead of pixels, use rem for fixed widths by calculating a px-to-rem ratio.

    Use min-width, max-width, or %: These properties help create a fully responsive site.

    For height, avoid setting fixed values when possible—use margin and padding instead.

    I hope this feedback was helpful

    Best, Teodor

    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

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