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

Results Summary UI with SCSS, HTML, and JSON Integration

animation, fetch
Natali 👻 Grimm•1,190
@Grimm-N
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?

🎉 What am I most proud of?.. Definitely how I managed to get through the project without breaking everything! 😅 From figuring out the grid layout to making those scores animate like a boss 💪, it's been a rollercoaster, but I’m proud that everything finally works and looks great (and nothing exploded... yet! 🤞).

What would I do differently next time? Oh, where do I begin? 😂 I’d probably double-check my CORS settings sooner rather than spending hours wondering why my JSON wasn’t loading 😅. And maybe, just maybe, I’d try not to procrastinate as much... but hey, who doesn't love a little last-minute adrenaline? 🚀

In the end, it’s all about learning, right? Next time, I’ll crush it even faster! 😎👊

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

💥 What challenges did I encounter? Oh boy, where do I start? First, there was the classic "Why isn't my fetch working?!" moment, which turned out to be a sneaky CORS issue. 😒 Then, my JSON data played a game of hide and seek with me. And don’t get me started on those animations—getting the scores to count up without breaking the internet felt like trying to train a cat to do tricks. 🐱✨

How did I overcome them? Lots of coffee, Google searches, and a sprinkle of sheer determination. ☕💻 I also realized that reading error messages actually helps (who knew, right? 🤷‍♀️). By the end of it, I became a master of grid layouts and timing functions—like a ninja coder but with slightly more caffeine jitters! 😅💪

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

🧐 What specific areas of my project would I like help with? Well, let’s just say I’ve got a pretty solid grip on most things... except maybe animations that look smooth and not like a choppy robot dance. 💃🤖 If someone could show me the secret sauce to flawless transitions, that would be awesome. Also, making sure my CSS is clean and not a spaghetti monster would be a dream come true. 🍝🎨

And hey, if you’ve got magical debugging skills, I’m all ears. My console and I are getting a bit too comfortable together. 😆🔍

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Natali 👻 Grimm's solution.

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.