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

Order Summary Component | Challange | Frontend Mentor

Nikhil Sajwan•30
@Nikhil-sajwan007
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?

One thing I'm particularly proud of in my frontend development journey is mastering responsive design techniques. Being able to create websites that adapt seamlessly to various screen sizes and devices is a significant achievement for me.

However, looking back, I realize that I could have paid more attention to optimizing performance. While my designs were visually appealing and functional, optimizing loading times and minimizing resource consumption could have enhanced the overall user experience.

In the future, I plan to prioritize performance optimization from the outset of a project. This might involve more diligent code reviews, utilizing performance monitoring tools, and staying updated on best practices in web development. Ultimately, by balancing aesthetics with performance, I aim to create even better user experiences in my future projects.

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

One of the challenges I encountered in my frontend development journey was mastering basic responsiveness. Initially, I struggled with ensuring that my designs looked and functioned well across different screen sizes and devices.

To overcome this challenge, I invested time in learning and practicing responsive design principles. I studied CSS media queries extensively to understand how to adjust layouts and styles based on viewport dimensions. Additionally, I utilized frameworks like Bootstrap, which provided built-in responsiveness features and helped streamline the development process.

Moreover, I actively sought feedback from peers and mentors, which allowed me to identify areas for improvement and refine my skills further. By continuously experimenting, testing, and iterating on responsive design techniques, I gradually became more proficient in creating adaptable and user-friendly interfaces.

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

In the context of this project, I would appreciate assistance with optimizing the CSS code for better performance and maintainability. Specifically, I'm looking for guidance on how to streamline my CSS styles, eliminate redundancy, and improve the overall structure of the codebase. Additionally, any advice on implementing best practices for responsive design would be valuable to ensure that the website functions flawlessly across various devices and screen sizes.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Nikhil Sajwan'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 1st-party linked stylesheets, and styles within <style> tags.

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.