Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Tailwind CSS for utility-first styling and responsive design

accessibility, pure-css, tailwind-css
MEHNOOR SHAHBAZ•720
@Mahnoor366880
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’m most proud of how I implemented the image carousel and lightbox functionality using JavaScript. It enhances the user experience by allowing smooth transitions between product images. Additionally, the responsive layout using Tailwind CSS, Flexbox, and CSS Grid makes the page visually appealing across different screen sizes.

Next time, I would focus more on refining the navigation bar styling to ensure consistent spacing and alignment. I would also improve the cart functionality by adding a mini-cart dropdown and an option to remove items dynamically. Moreover, I’d like to explore Next.js for better performance and scalability.

What challenges did you encounter, and how did you overcome them?
  1. Navigation Bar Spacing & Separation Line Challenge: The navbar didn’t have equal spacing on both sides, and the separation line wasn’t aligned properly. Solution: I used container mx-auto in Tailwind CSS to center the navbar and applied a border-b with limited width to align the separation line with the navigation links.

  2. Image Layout & Justification Challenge: The product image was taking up too much space, making the details section look too short in height and wide in width. Solution: I adjusted the grid layout, limiting the image section’s width and ensuring better proportion between the image and product details.

  3. Lightbox & Image Carousel Functionality Challenge: Implementing the lightbox while ensuring smooth navigation between images was tricky. Solution: I used JavaScript event listeners to dynamically update the lightbox image source, allowing users to click thumbnails to change the displayed image.

  4. Cart Quantity & Display Challenge: The cart quantity indicator wasn’t updating properly. Solution: I modified the JavaScript logic to ensure the count updates dynamically and remains visible when items are added to the cart.

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

Cart Functionality Improvements

Currently, the cart counter updates dynamically, but should I handle local storage to persist cart data on page reloads? Any insights, suggestions, or best practices to refine these areas would be greatly appreciated! 🚀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yamien Ariel•210
    @ariel172
    Posted 5 months ago

    great solution, but you could have come closer to the design

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