asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: migrated images to cloudinary from imgur (#2569)

Browse Source
This commit is contained in:
Shahed Nasser
2022-11-09 16:30:41 +02:00
committed by GitHub
parent 0a31ea9d43
commit 9e7e8c6d51
56 changed files with 326 additions and 328 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/content/advanced/backend/batch-jobs/index.md
+1 -1
View File
@@ -54,7 +54,7 @@ If the batch job fails at any point in this flow, its status is changed to `fail
:::
![Flowchart summarizing the batch job's flow from creation to completion](https://i.imgur.com/Qja0kAz.png)
![Flowchart summarizing the batch job's flow from creation to completion](https://res.cloudinary.com/dza7lstvk/image/upload/v1668001632/Medusa%20Docs/Diagrams/Qja0kAz_ns4vm8.png)
## What’s Next
docs/content/advanced/backend/notification/how-to-create-notification-provider.md
+2 -2
View File
@@ -267,11 +267,11 @@ You must be authenticated as an admin user before sending this request. You can
:::
![List Notifications Request](https://i.imgur.com/iF1rZX1.png)
![List Notifications Request](https://res.cloudinary.com/dza7lstvk/image/upload/v1668001650/Medusa%20Docs/Screenshots/iF1rZX1_msps2t.png)
Then, send a request to the [Resend Notification](https://docs.medusajs.com/api/admin/#tag/Notification/operation/PostNotificationsNotificationResend) endpoint using the ID retrieved from the previous request. You can pass the `to` parameter in the body to change the receiver of the notification. You should see the message “Notification Resent” in your console and if you implemented your own logic for resending the notification it will be resent.
![Resend Notifications Request](https://i.imgur.com/0zFfPed.png)
![Resend Notifications Request](https://res.cloudinary.com/dza7lstvk/image/upload/v1668001659/Medusa%20Docs/Screenshots/0zFfPed_og7one.png)
This request returns the same notification object as the List Notifications endpoint, but it now has a new object in the `resends` array. This is the resent notification. If you supplied a `to` parameter in the request body, you should see its value in the `to` property of the resent notification object.
docs/content/advanced/backend/payment/how-to-create-payment-provider.md
+1 -1
View File
@@ -40,7 +40,7 @@ All these methods must be declared async in the Payment Provider Service.
These methods are used at different points in the Checkout flow as well as when processing the order after it’s placed.
![Payment Flows.jpg](https://i.imgur.com/WeDr0ph.jpg)
![Checkout Flow - Payment](https://res.cloudinary.com/dza7lstvk/image/upload/v1668001750/Medusa%20Docs/Diagrams/WeDr0ph_idcrir.jpg)
## Create a Payment Provider
docs/content/advanced/backend/shipping/overview.md
+1 -1
View File
@@ -17,7 +17,7 @@ It’s also constructed to support multiple regions, provide different shipment
- **Shipping Options:** created by the admin and belong to a shipping profile. They are specific to certain regions and can have cart conditions. They use an underlying fulfillment provider. Once a customer checks out, they can choose the shipping option that’s available and most relevant to them.
- **Shipping Method:** created when the customer chooses a shipping option on checkout. The shipping method is basically a copy of the shipping option, but with values specific to the customer and the cart it’s associated with. When the order is placed, the shipping method will then be associated with the order and fulfilled based on the integration with the fulfillment provider.
![Shipping Architecture](https://i.imgur.com/QII2Hvn.png)
![Shipping Architecture](https://res.cloudinary.com/dza7lstvk/image/upload/v1668001762/Medusa%20Docs/Diagrams/QII2Hvn_vjkrdy.png)
## Fulfillment Provider