📘 Tutorial on how Sandbox is Used #381
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeff-matthews
added
the
major-update
…ce-docs/microsite-commerce-storefront into USF-2466-Sandbox-Tutorial
|
I will continue my review and walkthrough tomorrow when I'm back from PTO. |
…ce-docs/microsite-commerce-storefront into USF-2466-Sandbox-Tutorial
…ce-docs/microsite-commerce-storefront into USF-2466-Sandbox-Tutorial
…ce-docs/microsite-commerce-storefront into USF-2466-Sandbox-Tutorial
bdenham
reviewed
Aug 5, 2025
| Now we're ready to start building a composable frontend. Stop the server with `ctrl + c` and let's get started. | ||
|
|
||
| **Tip:** | ||
| Stop the server with `Ctrl + C`. | ||
| </Task> | ||
|
|
||
| <Task> | ||
| ### Generate a new UI Component |
There was a problem hiding this comment.
This topic needs more details about what a UI Component is in the context of drop-ins and what it's purpose is within the drop-in.
bdenham
reviewed
Aug 5, 2025
| These files were not only generated with the appropriate names, but they are completely preconfigured to work together as a unit. For example, the `LoginForm` component was automatically imported into `src/components/index.ts` to let you start referencing the component throughout your project. | ||
|
|
||
| And if you run `npm run dev` again, you'll see your new component in the Storybook UI, configured with an example and best practices to help you get started with Storybook. | ||
|
|
||
| </Task> | ||
|
|
||
| <Task> | ||
| ### Generate a new API Function |
There was a problem hiding this comment.
This topic needs more details about what the API function is for (provide examples) in the context of a drop-in.
bdenham
reviewed
Aug 5, 2025
|
|
||
| {/* TODO: Add code block of files generated */} | ||
|
|
||
| Review the files generated in `src/api/`. | ||
| </Task> | ||
|
|
||
| <Task> | ||
| ### Generate a Frontend Container |
There was a problem hiding this comment.
This topic needs more details about what a Container is in the context of drop-ins and what it's purpose is within the drop-in.
bdenham
requested changes
Aug 5, 2025
bdenham
requested changes
Aug 5, 2025
|
Superseded by #405 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
The current documentation for the dropin-template repo does not have a detailed explanation on how to get started with the Sandbox to preview built dropins. This PR adds fully detailed instructions to get started with the dropin-template sandbox.
Associated JIRA ticket
Jira ticket
Affected pages