Design comparison
Solution retrospective
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.
Community feedback
Please log in to post a comment
Log in with GitHubJoin 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