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

E-commerce product page built using Vite, Sass and Vue.js

sass/scss, vite, vue
David•70
@davidko5
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello there,

that's my second solution on this portal. I wanted to try new technologies such as Vite, Sass and Vue.js with Composition API.

I am mostly satisfied with the project, but I will be very grateful for your remarks and comments. The first thing I am not sure about is code quality, readability and maintainability. Secondly, I spent 3-4 days on this solution, and I am curious if it isn't too long for this kind of task?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • maicond•230
    @maicondguerian
    Posted over 2 years ago

    Hello David! Very nice and cleam project! I recently also start use Vite as a tool. You project is very smooth and similar to the challenge one the resolutions are quite close, one thing you could improve is the transition/animation on the cart and all hover elements to make it more smooth and soft, but you did a very good job! About the time you took do make in my opition its pretty acceptable as more you code more skills you get and can make it faster, anyway nice job!

    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