drawnjewellery.comThis is a jewellery ecommerce website based in UK. It was\nbuilt using Wordpress [https://wordpress.org/] + Woocommerce\n[https://woocommerce.com/] for the backend and NuxtJS [https://nuxtjs.org/] as\nthe frontend.\n\nThe backend was used as a headless CMS and using Woocommerce Store API\n[https://github.com/woocommerce/woocommerce-gutenberg-products-block/tree/trunk/src/StoreApi] \nto drive the data into the frontend (very experimental). I used Windi Css\n[https://windicss.org/] as the CSS framework, which I do prefer using over\nTailwind.\n\nMost of the available API they had was usable for the site but I had to custom\nmake the thank you page API where you can look back at this page for order\nsummary, order status providing you have the correct query key. (Just like the\nthank you page that you would find in Woocommerce normally).\n\nYou can make payments using Stripe [https://stripe.com/] (using Stripe elements\n[https://stripe.com/docs/stripe-js] to obtain the source token and then to pass\nthis token into Woocommerce) and also Paypal [https://paypal.com/]. For Paypal,\nthe site makes a request to Woocommerce with the order details and payment as\npaypal and awaits the response which in turn returns a redirection URL to the\nPaypal payment page. On payment complete the page will go to our thank you page\nand Paypal will use IPN to notify Woocommerce if the payment was successful or\nnot).\n\nThe project was definitely fun to work on but also quite challenging as the\navailable APIs were limited and had to either make my own endpoints or chain\nexisting APIs to get the data I needed, for example finding a product by slug\nwhen visiting the product page.\n\nNote: the API I think was not meant to be used in this way as it was built for\nits Glutenberg Woocommerce blocks, but I do think there is much potential for\nthe API to expand and give opportunities for developers to use it for other\nfrontend applications.