docs: change notes across docs based on redesign (#8662)
Change the prerequisites / soon / other notes based on latest redesign Depends on #8661
This commit is contained in:
@@ -8,13 +8,13 @@ In this chapter, you'll learn how to expose a hook in your workflow.
|
||||
|
||||
<Note title="Expose workflow hooks when" type="success">
|
||||
|
||||
- Your workflow is reusable in other applications, and you allow performing an external action at some point in your workflow.
|
||||
Your workflow is reusable in other applications, and you allow performing an external action at some point in your workflow.
|
||||
|
||||
</Note>
|
||||
|
||||
<Note title="Don't expose workflow hooks if" type="error">
|
||||
|
||||
- Your workflow isn't reusable by other applications. Use a step that performs what a hook handler would instead.
|
||||
Your workflow isn't reusable by other applications. Use a step that performs what a hook handler would instead.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ Medusa exposes hooks in many of its workflows that are used in its API routes. Y
|
||||
|
||||
<Note title="Consume workflow hooks when" type="success">
|
||||
|
||||
- You want to perform a custom action during a workflow's execution, such as when a product is created.
|
||||
You want to perform a custom action during a workflow's execution, such as when a product is created.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user