[CHEC-382] - Feature/pdp

[jaepass]

Making this a draft PR as there are still some kinks to work out. Hoping to get all UI components working on PDP first to avoid a large PR, and leave cart functionalities to Cart issue in next PR.

Working/changes:

• Categories on sidebar pulled from Redux store
• Data in PDP is rendered by dynamic route with getStaticProps() getStaticPaths() at page level
• Deprecated ProductHero and moved the dynamic Product content into ProductDetails, all other components on this page are rendered by pages/product/[permalink].js. Alternatively, pages/product/[permalink].js can be changed to pages/product/[permalink]/index.js
• variantSelector loops through available variants and available options within variant
• main product image is rendered three times as opposed to adding extra 2 images. Could add extra static images by mutating products in redux store.
• Kept SuggestedProducts same as ProductRow component rendering the latest 4 products. Or could alternatively render other products in same cat.

Not working/questions:

• the same carousel images on the side, not entirely sure how to approach this yet
• onSelectVariant toggling, need to tie the toggle or onSelectVariant to reflect price change
• can we keep the Shipping and Returns & Details as static data?

[linear[bot]]

CHEC-382 Individual product page

[robbieaverill]

can we keep the Shipping and Returns & Details as static data?

I think so

[ScopeyNZ]

• can we keep the Shipping and Returns & Details as static data?

Sounds good to me.

The other thing mentioned in the linear issue is the two descriptions - do you want to sort that out too?

I'm happy to merge this if you want to push forward, and then we can do PRs for each individual thing, rather than having this huge thing that's changing. Sound good?

[jaepass]

• can we keep the Shipping and Returns & Details as static data?

Sounds good to me.

The other thing mentioned in the linear issue is the two descriptions - do you want to sort that out too?

I'm happy to merge this if you want to push forward, and then we can do PRs for each individual thing, rather than having this huge thing that's changing. Sound good?

thanks Guy that sounds great if you're ok to merge then ill push on to the next thing! some of the issues involve quite a few files, should I be breaking larger issues those into sub issues?

[jaepass]

also i've connected the repo to Netlify but haven't built the project yet. Will wait until this is merged and will put up a live preview going forward

[ScopeyNZ]

Whatever makes sense Jaeriah. It doesn't usually matter how many files you touch in a PR, it just helps if the PR is focused on a clear (and small) goal, otherwise they blow up and include so much stuff that it's difficult to review.

[jaepass]

Whatever makes sense Jaeriah. It doesn't usually matter how many files you touch in a PR, it just helps if the PR is focused on a clear (and small) goal, otherwise they blow up and include so much stuff that it's difficult to review.

sounds good noted thanks Guy. will wait on your merge and jump on to the next thing

[ScopeyNZ]

Thank Jaeriah. I fixed up the Netlify stuff. Summary of what I did:

• Added a command to package.json that includes next export - a01dba1
• Updated Netlify config to run yarn deploy (what I added) - it was previously doing next-build which didn't exist
• Changed the output directory in Netlify from dist to out - that's default for Next I think
• Added the public key for the test store to environment variables on Netlify.