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

Summary Page using HTML,CSS

Kofi K•150
@Kofi100
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 was able to switch the main card from horizontal to vertical mode using CSS and being able to wrap a div element to the Summary title,making it effectively left-aligned.

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

Being able to switch from horizontal to vertical mode was a bit challenging but it was cool. The true challenge was using JavaScript to populate the webpage. I'll hopefully do it soon.

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

Any feedback on code and layout would be helpful. Thank you 🙏

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kathe•170
    @ktlamas29
    Posted 7 months ago

    Esta muy bien, solomente como sugerencia ponerle un sombreado para que resalte más la card del fondo.

    Marked as helpful
  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted 7 months ago

    Well done on this challenge! It looks good

    A few things you can do to make it better would be

    • Use more semantic HTML elements like sections, article, main. You should also make the h2 the first heading fo your website so no h3 should be before the h1. If you want it bold use strong or b tag. Also use p or span tags as well.
    • Responsiveness is good but you could try a mobile first approach next time to help make it easier to work with.

    For js once you get the data whether from fetching or turning it into a js file and importing it... You can setup an HTML template tag with the base structure of the results like image title and value/100.

    Then use JS to get that template and loop over your data and fill each template with its correct class name and data then append it the the container element. This is easier than using innerhtml and having the HTML code in a js string which won't let the code look elegant.

    Anyways take care!

    Marked as helpful
  • Nisha Kumari•300
    @technoish
    Posted 7 months ago

    This is a fantastic project! Adding subtle shadows to elements like .card or .card__box2 can create depth and make the design more dynamic. Try something like box-shadow: 0 10px 15px rgba(0, 0, 0, 0.2) for a polished and professional touch. Keep up the great work!

    Marked as helpful
  • Kofi K•150
    @Kofi100
    Posted 7 months ago

    Little thing guys,I've updated the webpage now. What do you think please?

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

Oops! 😬

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

Log in with GitHub