Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Angular, Heavy JSON work, multiple items available

angular, sass/scss, typescript
Nam Haϕ820
@Nam-Hai
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, Super exciting project for me and i'm glad to present my work to you. First Angular project for me, so it was very interesting to use typescript and scss for the first time. I had at first a hard time to implement all I wanted as I feel like it is a completely different experience from developpement in Javascript vanilla.

I'm pretty proud of the visual integration, i think this is pretty close to a "pixel perfect" integration. Both the modal and the hover effect on the image card was very interesting.

Conserning JSON, I have a surprise for you, I implemented other items. I think the right way to implement it would have been to use Angular Routing but I have a very not much experience with it and I thought about implementing other items too late in the developpement, it would have needed too much change in my code, so yeah. I just data-binded the title, the image, the price. The descriptive text is not data-binded because it would have give me too much imagination to write it all down lmao.

The cart gave me a lot of pain but it works wonder now. Deleting a single item was hard while traking the overall total of item in cart (which is display over the cart icon).

On a syntaxe point, it tottaly went over my head to be honest. I was a lot more focus on understaning Typescript and Component. Feel free to remind me things i forgot.

Side note, I started to use min-width which made easier the responsive side. I will try to use it a lot more in the futur.

Thx guys.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • utkuonursahin•295
    @utkuonursahin
    Posted over 3 years ago

    Congratulations, really cool stuff. As an advice, you can add a spinner while gallery images loading.

    Marked as helpful

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