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

Responsive E-Commerce Product Page by Tailwind CSS and Vanilla JS

tailwind-css
Eren•720
@erenymo
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 there 👋

Any feedback is welcome, Keep Coding ! ^^

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aman Singh Bhogal•1,010
    @asbhogal
    Posted almost 2 years ago

    Hi Eren,

    Great job! The design matches the mockups nicely and the app seems to function well. I've just listed some suggestions below in terms of code maintainability and performance:

    • Firstly, it's worth having separate JS files for your components (e.g. one for the slider, one for the cart handling.) This makes it easier to locate code and debug issues. If you use a bundler like Vite, this can make light work of it. You can them import them into your main.js, which is referenced in the index.html
    • Also, add your node_modules to your .gitignore as this bloats your build, and isn't required in production-ready interfaces. If a developer wants to run this on their local machine, its convention for them to run the npm install to install the relevant dependencies from the package.json lists, which would subsequently install the node_modules folder on their machine
    • Locally host your Google Fonts for privacy and performance reasons. Here's a link from Kevin Powell on how to download and convert them Link and a documentation link from Tailwind on how to reference them in your tailwind.config.js file (you can either extend or override the default theme) Link
    • In terms of accessibility, your button is missing an accessible name for screen readers and other assistive technologies to be able to read. Here's a link on how to add this Link
    • Your images are missing explicit height and width values, which can help prevent layout shifts on rendering
    • Use Vercel or Netlify for your front-end applications as these are much more robust platforms, compared to GitHub pages, with better performance, stability and caching. I use Vercel, and if you use Vite for your builds, it detects this and automatically compiles your code at build time when you push a commit to Git, meaning you don't have to run the npm script each time

    Hope this helps!

    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