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

Project tracking intro component

AlexCristea2007•840
@AlexCristea2007
A solution to the Project tracking intro 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 successfully develop the core functionalities of the shopping cart system, including adding and removing products, updating quantities, and ensuring that the checkout process worked smoothly. This process allowed me to create a clear flow for users to interact with the system, making sure each feature served its purpose efficiently. Overall, I felt like I was able to keep track of all the different moving parts, and things came together as expected.

In hindsight, I would focus more on improving the user interface to make it more intuitive and visually appealing. While the system functions as intended, enhancing the user experience could make a big difference in how users interact with the cart. Additionally, I would take more time to thoroughly test all the features, especially in edge cases, to avoid bugs or unexpected behavior. It would also be beneficial to optimize some of the backend processes, ensuring that the system performs better as the project scales.

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

One of the main challenges I faced was handling the cart's state across different pages. I had to ensure that the data, such as product quantities and details, would persist as users navigated through the system. Another difficulty was debugging issues that arose when updating quantities or removing products from the cart, especially when there were discrepancies between the displayed values and what was actually stored. Additionally, if integrating payment gateways was part of my project, ensuring secure and smooth transactions could pose further challenges.

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

Moving forward, I would greatly appreciate advice on how to optimize the checkout process. Ensuring a smooth and efficient user experience during this critical phase would be invaluable. I could also use guidance on managing large amounts of data, particularly when ensuring that the cart’s contents are consistent across multiple user sessions or devices. Lastly, it would be helpful to receive feedback on the project’s overall code structure, especially for scaling it in the future and ensuring it remains maintainable.

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 AlexCristea2007'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.