Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Full E-Commerce Site built using Next JS

motion, next, react, typescript, tailwind-css
Ollie•120
@OllieJ23
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 taking the initial front-end mentor challenge concept of a singular product page, and creating a full-stack e-commerce app using Next JS, typescript, tailwind etc.

I wanted to really challenge myself and test what i've learned already whilst introducing newer more complex ideas (such as SSR, CSR, cart functionalites and stores, payment functionality etc.) to showcase my ability to implement technical solutions whilst being able to creatively go off the initial 'mockup' brief of images.

If i were to do this differently, i would definitely start by using tailwinds - mobile first approach despite desktop being my innate preference. This is to ultimately familiarise myself with both workflows and also cater to tailwinds preference for styling.

What challenges did you encounter, and how did you overcome them?

The main challenges i encountered were the cart functionality, which i used Zustand to managed as it is a lightweight tool to manage state in next and was taught to me through series of youtube videos and a mixture of testing. Secondly the stripe payment functionality was new and difficult for me to adapt to, and i would say i am still definitely learning (and have more to learn) about managing seperate api routes to handle a backend server,

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

I would love help with more back-end features, specifically creating and management of seperate api routes in next js.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ollie's solution.

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

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.