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

Responsive Mobile-first product list with cart (Angular 18)

angular, typescript, rxjs
P
Ronan•310
@CannyRo
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?

I'm proud to have finished this challenge (and also to have deployed it... I fought for it! and I did it). If I had to do things differently, I wouldn't change a thing... because the main challenge for me was to do this project with Angular 18 to familiarize myself with it, relearn the basics, see the Signals and their power.

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

Each step was a difficulty in itself... or rather a learning experience. Thanks to the documentation... especially the documentation and a little help from ChatGPT to explain what I didn't understand, and don't worry, ChatGPT didn't do this challenge for me because he doesn't know Angular 18, or 17 for that matter... a version from which the framework has changed enormously, the documentation is on a different site, that's saying something...

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

Nothing in particular, but always open to comments and criticism that will help me improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted 8 months ago

    HI, Ronan, hope you're doing well! I loved how your project turned out, but I’ve got a few suggestions that could be useful:

    I noticed that your order confirmed modal is not centered, a tip I can give you so you can keep it centered and fixed on the screen:

    remove the paddings:

    @media (min-width: 1440px) {
        .modal--background[_ngcontent-ng-c109615066] {
            /* padding: 88px 40px; */
        }
    }
    @media (min-width: 768px) {
        .modal--background[_ngcontent-ng-c109615066] {
            /* padding: 40px; */
        }
    }
    

    and change position to fixed:

    .modal--background[_ngcontent-ng-c109615066] {
        display: none;
        position: fixed;
        inset: 0;
        justify-content: center;
        align-items: center;
        width: 100%;
        height: 100%;
        background-color: #00000080;
        z-index: 1000;
    }
    

    By doing this you will have a fixed and centralized modal on any device.

    The rest is fantastic.

    Hopefully, you'll find it helpful. 👍

    Marked as helpful
  • Andi Gashi•660
    @Andigashi1
    Posted 8 months ago

    Hi there and great job finishing this project!! I wanted to leave a comment to let you know that the layout in mobile view is not properly centered.

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.

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