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

E-commerce app with Shopify and Next.js

next, react
André-Lubin Thomas•330
@Lordyner
A solution to the Audiophile e-commerce website 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 being able to use Shopify GraphQL API to manage products. Next time I would create a better architecture for my projects. I'm used to develop website with 2-3 pages in React/Next.js, mostly landing page without data, so architecture was not my main concern.

But now I see that for a e-commerce app, I have to have something more structured to have a more maintable code and easily testable.

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

My biggest challenge was how to handle images. Because on shopify, there is only one field for images per product. So for one product, if we count the main image, the gallery image, the category image, the cart image, the preview image, times 3 (mobile/tablet/desktop).. that's a lot of image.

I started by adding all these images in this unique field, and fetch them all, then sort them depending on their name and their order. But it didn't look very maintainable because in a real situation, the owner of the shop would upload pictures. Impossible to make sure that he named well the images and order them properly.

Then I discovered the metafield and my life changed. 😂 The next challenge is about those metafield and how to fetch metafield of type file. The syntax was not really clear. To overcome it, I called a friend of mine, who is developer too, and I explain to him my problem. By explaining my problem, we were able to solve it.

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

I would like help with :

  • the UX/UI: what could be improve if it was a real website.
  • the architecture of my project : how can I structure my code better so it's more maintainable.
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 André-Lubin Thomas'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
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.