docs: publish restructure (#3496)

* docs: added features and guides overview page

* added image

* added version 2

* added version 3

* added version 4

* docs: implemented new color scheme

* docs: redesigned sidebar (#3193)

* docs: redesigned navbar for restructure (#3199)

* docs: redesigned footer (#3209)

* docs: redesigned cards (#3230)

* docs: redesigned admonitions (#3231)

* docs: redesign announcement bar (#3236)

* docs: redesigned large cards (#3239)

* docs: redesigned code blocks (#3253)

* docs: redesigned search modal and page (#3264)

* docs: redesigned doc footer (#3268)

* docs: added new sidebars + refactored css and assets (#3279)

* docs: redesigned api reference sidebar

* docs: refactored css

* docs: added code tabs transition

* docs: added new sidebars

* removed unused assets

* remove unusued assets

* Fix deploy errors

* fix incorrect link

* docs: fixed code responsivity + missing icons (#3283)

* docs: changed icons (#3296)

* docs: design fixes to the sidebar (#3297)

* redesign fixes

* docs: small design fixes

* docs: several design fixes after restructure (#3299)

* docs: bordered icon fixes

* docs: desgin fixes

* fixes to code blocks and sidebar scroll

* design adjustments

* docs: restructured homepage (#3305)

* docs: restructured homepage

* design fixes

* fixed core concepts icon

* docs: added core concepts page (#3318)

* docs: restructured homepage

* design fixes

* docs: added core concepts page

* changed text of different components

* docs: added architecture link

* added missing prop for user guide

* docs: added regions overview page (#3327)

* docs: added regions overview

* moved region pages to new structure

* docs: fixed description of regions architecture page

* small changes

* small fix

* docs: added customers overview page (#3331)

* docs: added regions overview

* moved region pages to new structure

* docs: fixed description of regions architecture page

* small changes

* small fix

* docs: added customers overview page

* fix link

* resolve link issues

* docs: updated regions architecture image

* docs: second-iteration fixes (#3347)

* docs: redesigned document

* design fixes

* docs: added products overview page (#3354)

* docs: added carts overview page (#3363)

* docs: added orders overview (#3364)

* docs: added orders overview

* added links in overview

* docs: added vercel redirects

* docs: added soon badge for cards (#3389)

* docs: resolved feedback changes + organized troubleshooting pages (#3409)

* docs: resolved feedback changes

* added extra line

* docs: changed icons for restructure (#3421)

* docs: added taxes overview page (#3422)

* docs: added taxes overview page

* docs: fix sidebar label

* added link to taxes overview page

* fixed link

* docs: fixed sidebar scroll (#3429)

* docs: added discounts overview (#3432)

* docs: added discounts overview

* fixed links

* docs: added gift cards overview (#3433)

* docs: added price lists overview page (#3440)

* docs: added price lists overview page

* fixed links

* docs: added sales channels overview page (#3441)

* docs: added sales overview page

* fixed links

* docs: added users overview (#3443)

* docs: fixed sidebar border height (#3444)

* docs: fixed sidebar border height

* fixed svg markup

* docs: added possible solutions to feedback component (#3449)

* docs: added several overview pages + restructured files (#3463)

* docs: added several overview pages

* fixed links

* docs: added feature flags + PAK overview pages (#3464)

* docs: added feature flags + PAK overview pages

* fixed links

* fix link

* fix link

* fixed links colors

* docs: added strategies overview page (#3468)

* docs: automated upgrade guide (#3470)

* docs: automated upgrade guide

* fixed vercel redirect

* docs: restructured files in docs codebase (#3475)

* docs: restructured files

* docs: fixed eslint exception

* docs: finished restructure loose-ends (#3493)

* fixed uses of backend

* docs: finished loose ends

* eslint fixes

* fixed links

* merged master

* added update instructions for v1.7.12

docs/content/development/services/create-service.md

@@ -0,0 +1,121 @@
+---
+description: 'Learn how to create a service in Medusa. This guide also includes how to use services in other services, subscribers, and endpoints.'
+addHowToData: true
+---
+
+# Create a Service
+
+In this document, you’ll learn how you can create a [Service](./overview.mdx) and use it across your Medusa backend just like any of the core services.
+
+## Implementation
+
+To create a service, create a TypeScript or JavaScript file in `src/services` to hold the service. The name of the file should be the registration name of the service without `Service` as it will be appended to it by default.
+
+For example, if you want to create a service `helloService`, create the file `hello.ts` in `src/services` with the following content:
+
+```ts title=/src/services/hello.ts
+import { TransactionBaseService } from "@medusajs/medusa"
+import { EntityManager } from "typeorm"
+
+class HelloService extends TransactionBaseService {
+  protected manager_: EntityManager
+  protected transactionManager_: EntityManager
+  getMessage() {
+    return `Welcome to My Store!`
+  }
+}
+
+export default HelloService
+```
+
+---
+
+## Service Constructor
+
+As the service extends the `TransactionBaseService` class, all services in Medusa’s core, as well as all your custom services, will be available in your service’s constructor using dependency injection.
+
+So, if you want your service to use another service, simply add it as part of your constructor’s dependencies and set it to a field inside your service’s class:
+
+```ts
+class HelloService extends TransactionBaseService {
+  private productService: ProductService
+
+  constructor(container) {
+    super(container)
+    this.productService = container.productService
+  }
+  // ...
+}
+```
+
+Then, you can use that service anywhere in your custom service:
+
+```ts
+class HelloService extends TransactionBaseService {
+  // ...
+  async getProductCount() {
+    return await this.productService.count()
+  }
+}
+```
+
+---
+
+## Use a Service
+
+In this section, you'll learn how to use services throughout your Medusa backend. This includes both Medusa's services and your custom services.
+
+:::note
+
+Before using your service, make sure you run the `build` command:
+
+```bash npm2yarn
+npm run build
+```
+
+:::
+
+### In a Service
+
+To use your custom service in another custom service, you can have easy access to it in the dependencies injected to the constructor of your service:
+
+```ts
+class MyService extends TransactionBaseService {
+  constructor(container) {
+    super(container)
+    this.helloService = container.helloService
+  }
+  // ...
+}
+```
+
+### In an Endpoint
+
+To use your custom service in an endpoint, you can use `req.scope.resolve` passing it the service’s registration name:
+
+```ts
+const helloService = req.scope.resolve("helloService")
+
+res.json({
+  message: helloService.getMessage(),
+})
+```
+
+### In a Subscriber
+
+To use your custom service in a subscriber, you can have easy access to it in the subscriber’s dependencies injected to the constructor of your subscriber:
+
+```ts
+class MySubscriber {
+  constructor({ helloService, eventBusService }) {
+    this.helloService = helloService
+  }
+  // ...
+}
+```
+
+---
+
+## See Also
+
+- [Create a Plugin](../plugins/create.md)