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

HTML5 ,CSS3, JAVASCRIPT, RESPONSIVE WEB DESIGN, UI/UX DESIGN PRINCIPLE

Solomon Obanijesu Philip•1,200
@Hackerbot24
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 AM PROUD OF COMPLETING MY FIRST FRONTENDMENTOR CHANLLAGE. SO VERY PROUD

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

ONE OF THE CHALLENGE I ENCOUNTER WAS IMPLEMENTING THE CART FUNCTIONALITY, BUT I HAD TO GO THROUGH MY STUDIES AGAIN TO GET IT, EVEN THOUGH IT TAKES ME DAYS

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

I THINK NO ONE IS AN HIGH LANDER I AM OPEN TO LEARNING

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted 12 months ago

    There is a lot I can say about this but let's start with well done, although the design isn't quite how it should look, the functionality ain't too bad either. I don't need to talk much about design wise as you would have the designs file, but I need to know why you didn't get to follow the design created. Anyways in terms of code now, you used the thumbnail photos which are low resolution so the images looks really blurry and pixelated, the thumbnails should only be used on the confirm order model nowhere else and so you know HTML has an inbuilt tag that's made for changing pictures based on screen sizes thats the <picture> element used with srcsets and img tag so that images can change naturally due to screen sizes. There is still so much you can improve upon and id gladly offer my help if you chose to accept it.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub