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

E-Commerce-Product-Page Built with HTML, CSS and ReactJS

react, semantic-ui
Emmanuel Oloke•320
@EmmanuelOloke
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I particularly chose this challenge to push my skills to the edge, I used the project to learn ReactJS, after watching numerous tutorials of course. It seemed like a small project, but I really learned a lot from it.

I decided not to use any UI library for styling as I wanted to test my CSS skills, but this decision led to me not being able to implement the mobile view menu, and image navigation for now. I will definitely make an update soon enough once I've learned even more ways to get it done.

One particular question I have for the community is, are there other ways to style SVG icons without directly manipulating them in the HTML code. Like changing the size (width and height), colour and adding state behaviours. I think having to write them directly into the HTML is a bit messy and if anyone has a clean and simple way to do this, I'm open to learning.

Over 10,000 people have started this challenge, and I'm glad I'm part of the 500+ people that have completed it.

As always, any other feedback will be really appreciated, Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adrian•280
    @Adrian397
    Posted over 3 years ago

    To manipulate svgs through CSS you can use e.g. fill, stroke-width, stroke (css properties). But before that i believe you have to delete them from html code (if there are any) to prioritize them in your's CSS code.

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