Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive e-commerce project

accessibility, bem, lighthouse
Doina•220
@Doileo
A solution to the E-commerce product page 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 most proud of my curiosity which led me to go beyond the project's requirements. This allowed me to create extra pages for each product model, add a sorting feature, and develop home, men, women, about, and contact pages.

Next time, there are a few things I would do differently:

  • Better Planning: I would spend more time planning the project and creating detailed sketches of the pages. This would make the development process smoother and reduce the need for big changes later on.

  • User Testing: I would do more user testing throughout the project. Getting feedback early would help me find and fix issues quickly and make sure the final product meets users' needs.

  • Code Optimization: I would focus on writing cleaner and more efficient code. Regularly improving and optimizing my code would make it run better and be easier to maintain.

By focusing on these areas, I aim to improve my process and deliver even better results in future projects.

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

For this project, I set the goal of using only vanilla JavaScript, which presented several challenges:

  • Integrating Features: One major challenge was ensuring all the features worked seamlessly together. To overcome this, I debugged each component, focusing on how they interacted. By breaking down the project into smaller tasks and tackling them individually, I successfully integrated all features.

  • Designing the Layout: Designing the layout for various pages was another challenge. To address this, I researched several e-commerce websites to gather inspiration and best practices. This research helped me create a functional and visually appealing design, and also provided new ideas for future projects.

  • Implementing Cart Functionality: Developing the cart functionality required precise handling of JavaScript events and state management. I tackled this by breaking down the cart operations (adding, removing, and updating items) into smaller functions, ensuring each part worked correctly before integrating them.

  • Adding Sorting Features: Implementing the sorting feature for the men's and women's pages involved manipulating the DOM and handling user inputs. By focusing on user experience, I ensured the sorting was intuitive and responsive.

By addressing these challenges and learning from each step, I completed the project successfully and gained valuable insights for future development work.

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

I would appreciate any feedback on my project. Learning from feedback is incredibly valuable to me, as it helps me understand what I did well and where I can improve. Your insights can guide me in refining my skills and making my future projects even better.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • DaniNewAcc•340
    @DaniNewAcc
    Posted about 1 year ago

    Hi, you have done a very cool project, one thing that can be done on the single product page is implementing the closing of the lightbox when the user click outside of it.. Other than that cursor: pointer when hovering on images and something that tells the user which image is selected like a different border color can give more user friendly design to the page.

    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