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

Responsive Product list with functional cart with Angular 18 & SASS!

accessibility, angular, rxjs, sass/scss, typescript
Ferdinando Geografo•370
@FerdinandoGeografo
A solution to the Product list with cart 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?

📌 In this funny Frontend Mentor Challenge I practiced a lot of layout organization and the way of thinking in a reusable way following the DRY principle.

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

💡 the main challenge was the management of the application state related to the products and cart data, and the shape of the possible actions to modify it, ensuring a decoupling between the components.

📚 I practiced and applied many of the principles also used by libraries such as NgRX : I delegated the entire management of the state to a service, with a pattern based on signals API provided by Angular and the actions callable by smart components to access data and modify them through methods provided by the service.

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

I would love to get some feedbacks from you. Your insights would be incredibly valuable in helping me improve. Here are a few specific areas where I'd appreciate your thoughts:

📌 Folder Structure Management:

How effective is the current folder structure? Are there any changes you would suggest to improve organization and maintainability?

📌 State Design and Action Management:

What do you think about the design of the state and the way actions are managed? Are there any best practices or improvements you would recommend?

📌 SCSS Organization:

How is the SCSS part of the application organized? Do you have any suggestions for better structuring or optimizing the SCSS?

📌 Possible Improvements or Suggestions:

Do you have any general feedback or suggestions for improving the solutions I've implemented? Are there any areas where you see potential for enhancement?

Thank you so much for taking the time to review my work. Your feedback is greatly appreciated ❤️.

Happy code to everyone!! 😁

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 Ferdinando Geografo'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.