docs: removed emojis (#2394)
This commit is contained in:
@@ -327,7 +327,7 @@ If you run your Gatsby storefront while the Medusa server is running, you should
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy your Medusa server](../deployments/server/index.mdx).
|
||||
- Learn how to [deploy your Gatsby storefront](../deployments/storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -308,7 +308,7 @@ Restart the Gatsby storefront then open a product that you added Rich Text conte
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to deploy your Medusa server to [Heroku](../../deployments/server/deploying-on-heroku.mdx), [Qovery](../../deployments/server/deploying-on-qovery.md), or [DigitalOcean](../../deployments/server/deploying-on-digital-ocean.md).
|
||||
- Learn [how to deploy your Gatsby storefront to Netlify](../../deployments/storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -274,7 +274,7 @@ If you make changes to the data while your Gatsby storefront is running, the cha
|
||||
|
||||
:::
|
||||
|
||||
## What’s Next :rocket:
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to customize your Contentful server and storefront](./customize-contentful.md).
|
||||
- Learn how to deploy your Medusa server to [Heroku](../../deployments/server/deploying-on-heroku.mdx), [Qovery](../../deployments/server/deploying-on-qovery.md), or [DigitalOcean](../../deployments/server/deploying-on-digital-ocean.md).
|
||||
|
||||
@@ -177,7 +177,7 @@ This will result in a subscription form similar to the following:
|
||||
|
||||
If you try entering an email and clicking Subscribe, the email will be subscribed to your Mailchimp newsletter successfully.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [SendGrid plugin](../add-plugins/sendgrid.mdx) for more Email functionalities.
|
||||
- [Learn more about plugins.](../advanced/backend/plugins/overview.md)
|
||||
|
||||
@@ -286,7 +286,7 @@ If you run your Gatsby storefront while the Medusa server and the MeiliSearch in
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy your Medusa server](../deployments/server/index.mdx).
|
||||
- Learn how to [deploy your Gatsby storefront](./../deployments/storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -199,6 +199,6 @@ module.exports = {
|
||||
|
||||
Where `127.0.0.1` is the domain of your local MinIO server.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [more plugins](https://github.com/medusajs/medusa/tree/master/packages) you can add to your store.
|
||||
|
||||
@@ -394,6 +394,6 @@ Clicking this button lets you capture the payment for an order. You can also ref
|
||||
|
||||
Refunding or Capturing payments is reflected in your PayPal dashboard as well.
|
||||
|
||||
## What's Next 🚀
|
||||
## What's Next
|
||||
|
||||
- Check out [more plugins](https://github.com/medusajs/medusa/tree/master/packages) you can add to your store.
|
||||
|
||||
@@ -170,7 +170,7 @@ module.exports = withStoreConfig({
|
||||
|
||||
Where `<BUCKET_NAME>` is the name of the S3 bucket you’re using.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [more plugins](https://github.com/medusajs/medusa/tree/master/packages) you can add to your store.
|
||||
- Learn how to [deploy the Medusa server](../deployments/server/index.mdx).
|
||||
|
||||
@@ -185,7 +185,7 @@ After adding the above subscriber, run your server again if it isn’t running a
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how [services](../advanced/backend/services/create-service.md) and [subscribers](../advanced/backend/subscribers/create-subscriber.md) work.
|
||||
- Check out a [full list of events](../advanced/backend/subscribers/events-list.md) in Medusa.
|
||||
|
||||
@@ -3961,7 +3961,7 @@ You can also track analytics related to emails sent from the SendGrid dashboard.
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about how [Notifications work in Medusa](../advanced/backend/notification/overview.md).
|
||||
- Install the [Medusa admin](https://github.com/medusajs/admin#-setting-up-admin) for functionalities like Gift Cards creation, swaps, claims, order return requests, and more.
|
||||
@@ -95,7 +95,7 @@ const plugins = [
|
||||
|
||||
That’s all you need to do to integrate Slack into Medusa!
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Install [Medusa's Admin](https://github.com/medusajs/admin) for the full order-management experience.
|
||||
- Add a Storefront to your Medusa server using [the Next.js starter](https://docs.medusajs.com/starters/nextjs-medusa-starter) or [the Gatsby starter](https://docs.medusajs.com/starters/gatsby-medusa-starter).
|
||||
|
||||
@@ -157,7 +157,7 @@ module.exports = withStoreConfig({
|
||||
|
||||
Where `<YOUR_SPACE_DOMAIN>` is the domain name for your Space which can be retrieved from the Space URL. For example, `medusa-server.fra1.digitaloceanspaces.com`.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [more plugins](https://github.com/medusajs/medusa/tree/master/packages) you can add to your store.
|
||||
- Learn how to [deploy the Medusa server on DigitalOcean](../deployments/server/deploying-on-digital-ocean.md).
|
||||
|
||||
@@ -172,7 +172,7 @@ Try updating any products on Strapi by going to Content Manager → Products and
|
||||
|
||||
If you try to update products on Medusa either using the [REST APIs](https://docs.medusajs.com/api/admin/#tag/Product/operation/PostProductsProduct) or using [the Medusa Admin](../user-guide/products/manage.mdx), you’ll see that the product is also updated on Strapi.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to deploy the Medusa server](../deployments/server/index.mdx).
|
||||
- Learn [how to create your own plugin](../advanced/backend/plugins/create.md).
|
||||
|
||||
@@ -356,6 +356,6 @@ Clicking this button allows you to capture the payment for an order. You can als
|
||||
|
||||
Refunding or Capturing payments is reflected in your Stripe’s dashboard as well. This gives you access to all of Stripe’s analytical capabilities.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [more plugins](https://github.com/medusajs/medusa/tree/master/packages) you can add to your store.
|
||||
|
||||
@@ -122,7 +122,7 @@ If you’re on a Twilio trial make sure that the phone number you entered on che
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about how [Notifications work in Medusa](../advanced/backend/notification/overview.md).
|
||||
- Install the [Medusa admin](../admin/quickstart.md) for functionalities like Gift Cards creation, swaps, claims, order return requests, and more.
|
||||
|
||||
@@ -113,7 +113,7 @@ Medusa admin provides a lot of ecommerce features including managing Return Merc
|
||||
|
||||
You can learn more about Medusa admin and its features in the [User Guide](../user-guide/index.mdx).
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Install the [Next.js](../starters/nextjs-medusa-starter.md) or [Gatsby](../starters/gatsby-medusa-starter.md) storefront starters.
|
||||
- [Learn how you can use `create-medusa-app` to install all of Medusa’s 3 components.](../usage/create-medusa-app.mdx)
|
||||
|
||||
@@ -288,7 +288,7 @@ After confirming the batch job, you can check the status while it is processing
|
||||
- If the status is `failed`, it means an error has occurred during the import. You can check the error in `result.errors`.
|
||||
- If the status is `completed`, it means the import has finished successfully.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [Batch Jobs and how they work](../backend/batch-jobs/index.md).
|
||||
- Check out the [Batch Jobs API Reference](https://docs.medusajs.com/api/admin/#tag/Batch-Job).
|
||||
|
||||
@@ -457,7 +457,7 @@ When you create or update a price list, you can specify one or more customer gro
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [Customer Groups](../backend/customer-groups/index.md).
|
||||
- Learn about [how to use Sales Channels](../backend/sales-channels/manage-admin.mdx).
|
||||
@@ -376,7 +376,7 @@ The batch job will start processing afterward. Based on the batch job strategy i
|
||||
|
||||
You can [retrieve the batch job](#optional-retrieve-batch-job) at any given point to check its status.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [batch jobs](./index.md).
|
||||
- Learn how to [import products using the Admin API](../../admin/import-products.mdx).
|
||||
|
||||
@@ -109,7 +109,7 @@ If you don’t want to overwrite Medusa’s batch job strategy, you can create a
|
||||
|
||||
For more details on creating custom batch job strategies, please check out the [Create Batch Job Strategy documentation](create.md).
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [batch jobs](./index.md).
|
||||
- Learn [how to use the Import Product APIs](../../admin/import-products.mdx).
|
||||
|
||||
@@ -123,6 +123,6 @@ To test the previous example out instantly, you can change the cron job expressi
|
||||
|
||||
:::
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [services and how you can use them](../services/overview.md).
|
||||
|
||||
@@ -54,7 +54,7 @@ The relation between the `PriceList` and `CustomerGroup` entities is available o
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to manage customer groups using the Admin APIs](../../admin/use-customergroups-api.mdx).
|
||||
- Learn more about [Price Lists and how they work](../price-lists/index.md).
|
||||
|
||||
@@ -214,7 +214,7 @@ export default (rootDirectory, pluginOptions) => {
|
||||
}
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- [Learn how to add an endpoint for the Storefront.](/advanced/backend/endpoints/add-storefront)
|
||||
- [Check out the API reference for all available endpoints.](https://docs.medusajs.com/api/admin)
|
||||
|
||||
@@ -213,7 +213,7 @@ export default (rootDirectory, pluginOptions) => {
|
||||
}
|
||||
```
|
||||
|
||||
## What’s Next :rocket:
|
||||
## What’s Next
|
||||
|
||||
- [Learn how to add an endpoint for the Admin.](/advanced/backend/endpoints/add-admin)
|
||||
- [Check out the API reference for all available endpoints.](https://docs.medusajs.com/api/store)
|
||||
|
||||
@@ -125,7 +125,7 @@ To delete soft-deletable entities that extend the `SoftDeletableEntity` class, y
|
||||
await postRepository.softDelete(post.id);
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out Medusa's entities in the [Entities' reference](../../../references/entities/classes/Address.md).
|
||||
- Learn about [migrations](../migrations/overview.md).
|
||||
|
||||
@@ -16,7 +16,7 @@ All entities must extend either the `BaseEntity` or `SoftDeletableEntity` classe
|
||||
|
||||
The `SoftDeletableEntity` class extends the `BaseEntity` class and adds another column `deleted_at`. If an entity can be soft deleted, meaning that a row in it can appear to the user as deleted but still be available in the database, it should extend `SoftDeletableEntity`.
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Learn [how to create an entity](./index.md).
|
||||
- Check out Medusa's entities in the [Entities' reference](../../../references/entities/classes/Address.md).
|
||||
@@ -85,7 +85,7 @@ If you had the feature flag previously enabled, and you want to disable this fea
|
||||
|
||||
You can follow [this documentation to learn how to revert the last migration you ran](https://docs.medusajs.com/cli/reference#migrations).
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [Migrations](../migrations/overview.md).
|
||||
- Learn how to [configure your Medusa server](../../../usage/configurations.md).
|
||||
|
||||
@@ -38,6 +38,6 @@ medusa migrations run
|
||||
|
||||
If you check your database now you should see that the change defined by the migration has been applied successfully.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [setting up your development server](../../../tutorial/0-set-up-your-development-environment.mdx).
|
||||
|
||||
@@ -48,7 +48,7 @@ npm run seed
|
||||
|
||||
This will use the underlying `seed` command provided by Medusa's CLI to seed your database with data from the file `data/seed.json` on your Medusa server.
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Learn [how to create a migration](index.md)
|
||||
- Learn more about [setting up your development server](../../../tutorial/set-up-your-development-environment).
|
||||
|
||||
@@ -264,7 +264,7 @@ Then, send a request to the [Resend Notification](https://docs.medusajs.com/api/
|
||||
|
||||
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.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out the [list of events](../subscribers/events-list.md) you can listen to.
|
||||
- Check out the [SendGrid](../../../add-plugins/sendgrid.mdx) plugin for easy integration of email notifications.
|
||||
|
||||
@@ -78,7 +78,7 @@ An example of a flow that can be implemented using Medusa's Notification API is
|
||||
- The customer returns the items triggering the `return.recieved` event.
|
||||
- The Notification Provider listens to the `return.received` event and sends an email to the customer with confirmation that their items have been received and that a refund has been issued.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [create your own Notification Provider](how-to-create-notification-provider.md).
|
||||
- Check out the [list of events](../subscribers/events-list.md) in Medusa.
|
||||
|
||||
@@ -381,7 +381,7 @@ async retrieveSavedMethods(customer) {
|
||||
}
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out the Payment Providers for [Stripe](https://github.com/medusajs/medusa/tree/2e6622ec5d0ae19d1782e583e099000f0a93b051/packages/medusa-payment-stripe) and [PayPal](https://github.com/medusajs/medusa/tree/2e6622ec5d0ae19d1782e583e099000f0a93b051/packages/medusa-payment-paypal) for implementation examples.
|
||||
- Learn more about the [frontend checkout flow](./../../storefront/how-to-implement-checkout-flow.mdx).
|
||||
|
||||
@@ -118,7 +118,7 @@ If then the request is interrupted for any reason or the payment fails, the clie
|
||||
|
||||
This prevents any payment issues from occurring with the customers and allows for secure retries of failed payments or interrupted connections.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- [Check out how the checkout flow is implemented on the frontend.](./../../storefront/how-to-implement-checkout-flow.mdx)
|
||||
- Check out payment plugins like [Stripe](../../../add-plugins/stripe.md), [Paypal](/add-plugins/paypal), and [Klarna](../../../add-plugins/klarna.md).
|
||||
|
||||
@@ -455,7 +455,7 @@ To install any published plugin, you can run the following command on any Medusa
|
||||
npm install medusa-plugin-custom
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out [available Services in Medusa](references/services/../../../../../references/services/classes/AuthService.md) that you can use in your plugin.
|
||||
- Check out [available events](../subscribers/events-list.md) that you can listen to in Subscribers.
|
||||
|
||||
@@ -48,7 +48,7 @@ If you’re installing an official plugin from the Medusa repository, you can fi
|
||||
|
||||
For community plugins, please refer to the installation instructions of that plugin to learn about any required configurations.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [create your own plugin](create.md).
|
||||
- Learn how to [create a fulfillment provider](../shipping/add-fulfillment-provider.md) or a [payment provider](../payment/how-to-create-payment-provider.md).
|
||||
|
||||
@@ -81,7 +81,7 @@ Since the line item belongs to a cart, there’s no need to pass the `region_id`
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [price selection strategies](../price-selection-strategy/index.md).
|
||||
- Learn [how to use the PriceList Admin APIs](./use-api.mdx).
|
||||
|
||||
@@ -466,7 +466,7 @@ This request returns the ID of the deleted price list.
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [price lists](./index.md).
|
||||
- Learn how the [price selection strategy works](../price-selection-strategy/index.md).
|
||||
@@ -60,7 +60,7 @@ The context that is passed to the `calculateVariantPrice` method is an object th
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to override the price selection strategy](./override.md).
|
||||
- Learn more about [price lists](./../price-lists/index.md).
|
||||
|
||||
@@ -106,6 +106,6 @@ Then, try out your strategy using any of the [Products](https://docs.medusajs.co
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [price list selection strategy](./index.md).
|
||||
|
||||
@@ -68,7 +68,7 @@ The relation is implemented in the [Order](../../../references/entities/classes/
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [manage Sales Channels using the Admin APIs](./manage-admin.mdx).
|
||||
- Check out the [Sales Channel’s Admin APIs](https://docs.medusajs.com/api/admin/#tag/Sales-Channel).
|
||||
|
||||
@@ -517,6 +517,6 @@ The request returns an array of orders that are associated with the specified sa
|
||||
|
||||
---
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [Sales Channels and how they work](./index.md).
|
||||
@@ -90,7 +90,7 @@ constructor({ helloService, eventBusService }) {
|
||||
}
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out the [Services Reference](/references/services/classes/AuthService) to see a list of all services in Medusa.
|
||||
- [Learn How to Create an Endpoint.](/advanced/backend/endpoints/add-storefront)
|
||||
|
||||
@@ -18,7 +18,7 @@ For example, if the file name is `hello.js`, the service will be registered as `
|
||||
|
||||
The registration name of the service is important, as you’ll be referring to it when you want to get access to the service using dependency injection or in routes.
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Learn [how to create a service](./create-service.md)
|
||||
- Check out the [Services Reference](/references/services/classes/AuthService) to see a list of all services in Medusa.
|
||||
|
||||
@@ -266,7 +266,7 @@ cancelFulfillment(fulfillment) {
|
||||
}
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out the [Webshipper plugin](https://github.com/medusajs/medusa/tree/cab5821f55cfa448c575a20250c918b7fc6835c9/packages/medusa-fulfillment-webshipper) for an example of a fulfillment provider that interacts with a third-party providers.
|
||||
- Check out the [manual fulfillment plugin](https://github.com/medusajs/medusa/tree/cab5821f55cfa448c575a20250c918b7fc6835c9/packages/medusa-payment-manual) for a basic implementation of a fulfillment provider.
|
||||
|
||||
@@ -135,7 +135,7 @@ The `ShippingMethod` also belongs to the `Order` entity. This association is
|
||||
|
||||
The `ShippingMethod` instance holds a `price` attribute, which will either be the flat rate price or the calculated price.
|
||||
|
||||
## What’s Next :rocket:
|
||||
## What’s Next
|
||||
|
||||
- [Learn how to Create a Fulfillment Provider.](./add-fulfillment-provider.md)
|
||||
- Check out [available shipping plugins](https://github.com/medusajs/medusa/tree/master/packages).
|
||||
|
||||
@@ -71,7 +71,7 @@ constructor({ productService, eventBusService }) {
|
||||
|
||||
You can then use `this.productService` anywhere in your subscriber’s methods.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- [View the list of all events](events-list.md)
|
||||
- [Learn how to create a service.](/advanced/backend/services/create-service)
|
||||
|
||||
@@ -2153,7 +2153,7 @@ Object of the following format:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how you can [use services in subscribers](create-subscriber.md#using-services-in-subscribers).
|
||||
- Learn how to [create notifications](../notification/overview.md) in Medusa.
|
||||
|
||||
@@ -20,7 +20,7 @@ Custom subscribers reside in your project's `src/subscribers` directory. Files h
|
||||
|
||||
Whenever an event is emitted, the subscriber’s registered handler method is executed. The handler method receives as a parameter an object that holds data related to the event. For example, if an order is placed the `order.placed` event will be emitted and all the handlers will receive the order id in the parameter object.
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Learn [how to create a Subscriber](create-subscriber.md).
|
||||
- [View the list of all events](events-list.md).
|
||||
|
||||
@@ -187,7 +187,7 @@ The relevant fields are:
|
||||
|
||||
During the calculation of the totals of different components of the cart or order, such as shipping or line items, if tax inclusivity is enabled on that component, a process similar to those explained above will be applied to retrieve the total.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [calculate taxes manually](manual-calculation.md).
|
||||
- [Check out the API reference](https://docs.medusajs.com/api/store/).
|
||||
|
||||
@@ -82,7 +82,7 @@ You can learn how to [retrieve and use services](../services/create-service.md#u
|
||||
|
||||
:::
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn about [tax-inclusive pricing](inclusive-pricing.md).
|
||||
- Learn about available methods in [CartsService](../../../references/services/classes/CartService.md) and [TotalsService](../../../references/services/classes/TotalsService.md).
|
||||
|
||||
@@ -358,7 +358,7 @@ The request returns two properties: `type` and `data`. If the order was placed s
|
||||
|
||||
If an error occurred while placing the order, `type` will be `cart` and `data` will be the cart's data.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about the [JS Client and how to use it](../../js-client/overview.md).
|
||||
- Check out available plugins for popular payment providers such as [Stripe](../../add-plugins/stripe.md) and [PayPal](/add-plugins/paypal.md).
|
||||
|
||||
@@ -206,7 +206,7 @@ medusa telemetry
|
||||
| `--enable` | Enable telemetry (default) |
|
||||
| `--disable` | Disable telemetry |
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn more about [anonymous usage data collection](../usage.md).
|
||||
- Learn how to [configure your Medusa server](../usage/configurations.md).
|
||||
|
||||
@@ -269,7 +269,7 @@ Where `<ADMIN_URL>` is the URL of your Medusa Admin that you just deployed.
|
||||
|
||||
Then, restart your Medusa server. Once the server is running again, you can log in to the Medusa Admin and use it.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy your storefront](../storefront/index.mdx).
|
||||
- Learn more about [how you can configure Medusa](../../usage/configurations.md).
|
||||
|
||||
@@ -275,7 +275,7 @@ Then, scroll down and find Environment Variables. You can expand the environment
|
||||
|
||||
Once you click Save, the environment variables will be saved and a redeployment will be triggered.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to deploy the Medusa Admin to Netlify](../admin/deploying-on-netlify.md).
|
||||
- Learn [how to deploy the Gatsby Storefront to Netlify](../storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -280,7 +280,7 @@ heroku config:set <ENV_NAME>=<ENV_VALUE> -a <APP_NAME>
|
||||
|
||||
Where `<APP_NAME>` is the name of your Heroku app, `<ENV_NAME>` is the name of the environment variable, and `<ENV_VALUE>` is the value.
|
||||
|
||||
## What's Next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Learn how to [deploy your Medusa admin](../admin/index.mdx).
|
||||
- Learn how to [deploy your storefront](../storefront/index.mdx).
|
||||
|
||||
@@ -502,7 +502,7 @@ To add environment variables, in your [Qovery Console](https://console.qovery.co
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy the Medusa Admin to Netlify](../admin/deploying-on-netlify.md).
|
||||
- Learn how to [deploy the Gatsby Storefront to Netlify](../storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -305,7 +305,7 @@ Where `<STOREFRONT_URL>` is the URL of your Gatsby storefront that you just depl
|
||||
|
||||
Then, restart your Medusa server. Once the server is running again, you can use your Gatsby storefront.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy the Medusa Admin](../admin/index.mdx).
|
||||
- Learn more about [Medusa’s configurations](../../usage/configurations.md).
|
||||
|
||||
@@ -385,7 +385,7 @@ This request accepts the ID of the cart and the ID of the line item as path para
|
||||
|
||||
It returns the updated cart.
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn [how to implement the checkout flow in your storefront](../advanced/storefront/how-to-implement-checkout-flow.mdx).
|
||||
- Learn more about the [JS Client and how to use it](../js-client/overview.md).
|
||||
|
||||
@@ -58,7 +58,7 @@ Medusa provides two starter storefronts, one built with [Next.js](./starters/nex
|
||||
|
||||
Alternatively, you can build your own storefront with any frontend framework of your choice just by connecting to your server with the [Storefront REST APIs](https://docs.medusajs.com/api/store).
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Customize your Medusa server by creating your own [endpoints](./advanced/backend/endpoints/add-storefront.md), [services](./advanced/backend/services/create-service.md), and [subscribers](./advanced/backend/subscribers/create-subscriber.md).
|
||||
- Check out guides under the Integrations section to install plugins for [CMS](./add-plugins/strapi.md), [Payment](./add-plugins/stripe.md), [Search Engines](./add-plugins/algolia.md), and more.
|
||||
|
||||
@@ -98,7 +98,7 @@ It's important to configure your Medusa server properly and learn how environmen
|
||||
|
||||
You can learn more about configuring your server and loading environment variables in the [Configure your Server documentation](../usage/configurations.md).
|
||||
|
||||
## What's next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Install the [Next.js](../starters/nextjs-medusa-starter.md) or [Gatsby](../starters/gatsby-medusa-starter.md) storefronts to set up your ecommerce storefront quickly.
|
||||
- Install the [Medusa Admin](../admin/quickstart.md) to supercharge your ecommerce experience with easy access to configurations and features.
|
||||
|
||||
@@ -79,7 +79,7 @@ To upload product images to your Medusa server, you must install and configure o
|
||||
- [S3](../add-plugins/s3.md)
|
||||
- [DigitalOcean Spaces](../add-plugins/spaces.md)
|
||||
|
||||
## What's next :rocket:
|
||||
## What's Next
|
||||
|
||||
- Install the [Next.js](../starters/nextjs-medusa-starter.md) or [Gatsby](../starters/gatsby-medusa-starter.md) storefronts to set up your ecommerce storefront.
|
||||
- Install the [Medusa Admin](../admin/quickstart.md) to supercharge your ecommerce experience with easy access to configurations and features.
|
||||
|
||||
@@ -107,7 +107,7 @@ The Gatsby storefront comes with a lot of features out of the box including:
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check the [Storefront API reference](https://docs.medusajs.com/api/store) for a full list of REST APIs to use on your storefront.
|
||||
- Learn how to [deploy the Gatsby storefront on Netlify](../deployments/storefront/deploying-gatsby-on-netlify.md).
|
||||
|
||||
@@ -212,7 +212,7 @@ You can learn more about development with Next.js through [their documentation](
|
||||
|
||||

|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check the [Storefront API reference](https://docs.medusajs.com/api/store) for a full list of REST APIs to use on your storefront.
|
||||
- Learn [how to install Medusa Admin](../admin/quickstart.md).
|
||||
|
||||
@@ -251,7 +251,7 @@ To install Redis without Homebrew you can check out [Redis’s guide on installi
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [configure your Medusa server](../usage/configurations.md).
|
||||
- Learn how to install a storefront with [Next.js](../starters/nextjs-medusa-starter.md) or [Gatsby](./../starters/gatsby-medusa-starter.md).
|
||||
|
||||
@@ -306,7 +306,7 @@ It is recommended to use environment variables to store values of options instea
|
||||
|
||||
:::
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out the [Next.js](../starters/nextjs-medusa-starter.md) and [Gatsby](../starters/gatsby-medusa-starter.md) starter storefronts.
|
||||
- Install the [Medusa admin](../admin/quickstart.md).
|
||||
|
||||
@@ -86,7 +86,7 @@ Learn more about the [Next.js](../starters/nextjs-medusa-starter.md) and [Gatsby
|
||||
After choosing the above starters, the installation of each component will begin along with its dependencies. Once the installation is done, you’ll see instructions related to how to start each component.
|
||||
|
||||
```bash
|
||||
Your project is ready 🚀. The available commands are:
|
||||
Your project is ready. The available commands are:
|
||||
|
||||
Medusa API
|
||||
cd my-medusa-store/backend
|
||||
@@ -114,7 +114,7 @@ Inside the root project directory which was specified at the beginning of the in
|
||||
/admin // Medusa admin panel
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Learn how to [deploy the Medusa server](../deployments/server/index.mdx).
|
||||
- Learn how to [deploy the Medusa admin](../deployments/admin/index.mdx).
|
||||
|
||||
@@ -178,7 +178,7 @@ medusa-dev -q
|
||||
medusa-dev --packages @medusajs/medusa-cli medusa-file-minio
|
||||
```
|
||||
|
||||
## What’s Next 🚀
|
||||
## What’s Next
|
||||
|
||||
- Check out our [contribution guidelines](https://github.com/medusajs/medusa/blob/master/CONTRIBUTING.md).
|
||||
- Learn how to [create a plugin](../advanced/backend/plugins/create.md).
|
||||
|
||||
Reference in New Issue
Block a user