Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Updated Ecommerce product page main - HTML, CSS, JS

accessibility
P
Aydan•680
@AydanKara
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 how i improved upon my previous solution by applying new techniques and best practices i’ve learned over the past year. This project is an updated version of a challenge i previously completed, but this time, i focused on writing cleaner, more maintainable, and scalable code.

Next time:

  • Using JavaScript framework/library (like React) to improve state management and component reusability.

  • HTML improving by further optimizing accessibility features (e.g., ARIA attributes).

What challenges did you encounter, and how did you overcome them?
  • Handling a large CSS file: I initially had all styles in one file, making it difficult to maintain. I resolved this by splitting styles into multiple smaller files (e.g., typography, layout, components).

  • JavaScript event handling: Managing different UI interactions (menu toggle, cart updates) in pure JavaScript required careful structuring. I overcame this by modularizing JavaScript and splitting it into separate files ensuring each function had a clear role.

  • Ensuring a clean HTML structure: I had to refactor some parts of HTML to remove unnecessary divs and ensure better readability and maintainability.

What specific areas of your project would you like help with?
  • HTML structure: Are there any improvements that could be useful for better accessibility and SEO?

  • JavaScript code: Is the JavaScript optimized for performance and scalability, or are there areas where it could be improved?

  • CSS best practices: What additional techniques can we use to improve maintainability and performance?

I would appreciate any feedback on how to further optimize and scale the project. Thanks for your insights!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    RF13•610
    @rf1303
    Posted about 1 month ago

    Muy buen trabajo , prolijo y los modulos de javascript, lo unico que falta es que no funciona el cambio de imagen en mobile y tablet

    felicitaciones se ve muy bien!

    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