Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Order Summary Project

shammah john•40
@uwenvati
A solution to the Order 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 most proud of the responsiveness and clean design I achieved. I focused a lot on ensuring that the layout looked great on both desktop and mobile devices, which involved a lot of media queries and flexible units. Also, I’m really happy with the smooth animations and transitions that add a touch of interactivity without being overwhelming. Seeing everything come together as a polished, user-friendly interface was incredibly satisfying. Next time, I’d plan the project structure more thoroughly before jumping into coding. I realized halfway through that some of my initial decisions on file organization and component structure weren’t the most efficient, which made things a bit messy to manage. I’d also like to spend more time on accessibility features, ensuring the site is usable for people with various disabilities. Lastly, I’d like to experiment more with modern CSS features like Grid and Flexbox to improve the layout even further.

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

One of the biggest challenges I encountered was making sure the layout was perfectly responsive across different devices. Initially, some elements didn’t scale as expected, causing a few headaches with alignment and spacing. I overcame this by diving deeper into CSS Grid and Flexbox, which provided a more robust solution for creating flexible layouts.

Another challenge was optimizing the images for different screen sizes to maintain a balance between visual quality and loading speed. I tackled this by using the srcset attribute and different image formats, ensuring that the appropriate image was loaded for each device.

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

I’d love some help with the following areas of my project:

Accessibility: While I tried to follow best practices, I’m not entirely confident that the site is fully accessible. Guidance on improving keyboard navigation, ARIA roles, and ensuring compatibility with screen readers would be invaluable.

Performance Optimization: I want to ensure that the site loads quickly and performs smoothly, especially on mobile devices with slower connections. Any tips on further optimizing images, reducing render-blocking resources, and improving overall load times would be greatly appreciated.

Advanced CSS Techniques: I’m keen to learn more about advanced CSS, particularly Grid and Flexbox layouts. While I used these tools, I feel there’s a lot more I could do to refine my layouts and make them even more responsive and elegant.

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 shammah john'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

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.