Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 19 days ago

cards made using css grid, used flexbox to align items, used media que

Siddharth-esc•20
@Siddharth-esc
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?

i'm glad that that i have completed this project in a short span of time. one of the things that i will do differently next time is breaking stuff into smaller parts and checking how each item works as per the responsiveness which will save a lot of my time.

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

there were not any major problems in this challenge, although i faced one will positioning the footer which was malfunctioning.

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

how to prevent malfunctioning in media queries and also while adding new elements in html.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,430
    @thisisharsh7
    Posted 19 days ago

    Great job completing the challenge!

    Strengths:

    • Clean Design: The gradient backgrounds and card styling are well-executed, matching the design.
    • Clear Structure: The HTML is organized, with distinct sections for the result and summary cards.

    Some suggestions:

    • Media Query Malfunction: The footer (attribution) positioning issues stem from multiple media queries overriding bottom. Consolidate into one media query (e.g., @media (max-width: 640px)) and adjust bottom dynamically (e.g., bottom: calc(-300px - 10vw)) to avoid overlap across screen sizes.
    • Adding New Elements: When adding elements, ensure they respect the existing flex/grid layouts. Test new elements in both desktop and mobile views to avoid breaking responsiveness. Use box-sizing: border-box consistently to prevent padding/margin issues.
    • Accessibility: Add alt text to images (e.g., alt="Reaction icon") for screen readers.
    • CSS Optimization: Use CSS custom properties for colors (e.g., --red: #ff5757) to simplify maintenance.
    • Footer Fix: Move .attribution outside .card-container to avoid layout conflicts.

    Breaking tasks into smaller parts, as you plan, will help! Solid work overall.

    Marked as helpful
  • fisherstack•120
    @fisherstack
    Posted 19 days ago

    Nice job :) That's interesting : I didn't though of that way of managing the white background (for the second card, with a negative margin) : i treated the white background as the main background (less minus values for lazy persons like me ^^).

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