L320workbook #211
L320workbook #211
Conversation
…storefront into Lab320
Co-authored-by: Natxo Cabré <[email protected]>
Co-authored-by: Natxo Cabré <[email protected]>
bdenham
requested review from
tkacheva and
jeff-matthews
and removed request for
tkacheva
There was a problem hiding this comment.
Looks great! I like the new nav pattern for developers and merchants.
I just have some minor editorial comments about formatting. The flow makes sense.
The only thing I'm wondering about is: what happens if we deploy this to prod and someone who isn't attending the lab attempts it?
- Will they be able to do it? If so, for how long before some lab resource is decommissioned?
- How are you envisioning the transition to evergreen use case docs post-Summit lab?
src/content/docs/merchants/tutorials/summit-lab-320/create-product-page.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/merchants/tutorials/summit-lab-320/create-product-page.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| <Steps> | ||
| 1. Navigate to folder `products`. | ||
| 1. Create a folder called `apple-iphone-13`. |
There was a problem hiding this comment.
| 1. Create a folder called `apple-iphone-13`. | |
| 1. Create a folder named `apple-iphone-13`. |
src/content/docs/merchants/tutorials/summit-lab-320/create-product-page.mdx
Outdated
Show resolved
Hide resolved
| ### Preview the page | ||
|
|
||
| <Steps> | ||
| 1. Click the instant **Preview** button. |
There was a problem hiding this comment.
I'm assuming that's the paper plane icon based on the lab warm up, but this still made me pause.
There was a problem hiding this comment.
Actually, no. I'm referring to a different button than the paper plane Action button. So that's a good, valid callout. I need to find a nice solution for inline button images.
src/content/docs/merchants/tutorials/summit-lab-320/create-product-page.mdx
Outdated
Show resolved
Hide resolved
| <Steps> | ||
| 1. Insert a new —*Section Break*— directly after the Hero block's `section-metadata` using the **Section Break** tool in the Edit menu. | ||
| 1. Insert a **`targeted-block fragment`** from `Library > Blocks > Targeted Blocks`. |
There was a problem hiding this comment.
I don't think Library > Blocks > Targeted Blocks should be code formatted. We use bolding elsewhere.
|
|
||
| <Steps> | ||
| 1. From the home page preview, select `Account > Login` from the site's navigation menu and enter these credentials: |
There was a problem hiding this comment.
I don't think Account > Login should be code formatted. We use bolding elsewhere.
| 1. Open the `cart` document in your project root. | ||
| 1. Insert a new —*Section Break*— directly after the `commerce-cart` **metadata** block using the **Section Break** tool in the Edit menu. | ||
| 1. Insert a **`targeted-block fragment`** from `Library > Blocks > Targeted Blocks`. |
There was a problem hiding this comment.
I don't think Library > Blocks > Targeted Blocks should be code formatted. We use bolding elsewhere.
| <Steps> | ||
| 1. Click the **Action** button (paper plane icon), select **Preview**. | ||
| 1. Login to the site as a Plan-Connect customer (`Account > Login`) and enter the following credentials: |
There was a problem hiding this comment.
I don't think Account > Login should be code formatted. We use bolding elsewhere.
|
@jeff-matthews, yeah, all great questions. After I generate the PDF for the lab later tonight, I’ll think it through to find a solution for publishing to production tomorrow afternoon. Stay tuned! |
…duct-page.mdx Co-authored-by: Jeff Matthews <[email protected]>
Co-authored-by: Jeff Matthews <[email protected]>
This PR takes the place of Lab320 to invite last updates and reviews, including Olena T's addition content.
Reviewer Instructions
Review the following four files. The files will be generated into the PDF lab workbook for Summit: