Merge pull request #124 from ueberdosis/feature/conversion-support-v1

Adjusted commands and configurations

Author: ThisDavidRichard

src/content/conversion/import-export/docx/custom-mark-conversion.mdx

@@ -9,15 +9,15 @@ meta:
 import { Callout } from '@/components/ui/Callout'
 import { CodeDemo } from '@/components/CodeDemo'
 
-When importing a DOCX file, you can also define how custom marks should be converted back to Tiptap nodes. This is done by passing an array of custom mark definitions to the `import` command. You could use this feature to convert your custom stylings from Word into Titap with ease.
+When importing a DOCX file, you can also define how custom marks should be converted back to Tiptap nodes. This is done by passing an array of custom mark definitions to the `importDocx` command. You could use this feature to convert your custom stylings from Word into Titap with ease.
 
 ```ts
-import { Import } from '@tiptap-pro/extension-import'
+import { ImportDocx } from '@tiptap-pro/extension-import-docx'
 
 const editor = new Editor({
   extensions: [
     // Other extensions ...
-    Import.configure({
+    ImportDocx.configure({
       appId: 'your-app-id',
       token: 'your-jwt',
       // ATTENTION: This is for demo purposes only
@@ -35,7 +35,7 @@ const editor = new Editor({
 })
 ```
 
-The latest version of the `@tiptap-pro/extension-import` has the `prosemirrorMarks` configuration option available.
+The latest version of the `@tiptap-pro/extension-import-docx` has the `prosemirrorMarks` configuration option available.
 
 This option allows you to map custom nodes from the DOCX to your Tiptap schema. In the example above, we are mapping the `bold` and `italic` nodes from the DOCX to the `strong` and `em` nodes in our Tiptap schema.
 

src/content/conversion/import-export/docx/custom-node-conversion.mdx

@@ -9,7 +9,7 @@ meta:
 import { Callout } from '@/components/ui/Callout'
 import { CodeDemo } from '@/components/CodeDemo'
 
-One of the biggest advantages of the `@tiptap-pro/extension-export-docx` and `@tiptap-pro/extension-import` extensions is the ability to define how custom nodes in your Tiptap schema should be rendered in DOCX.
+One of the biggest advantages of the `@tiptap-pro/extension-export-docx` and `@tiptap-pro/extension-import-docx` extensions is the ability to define how custom nodes in your Tiptap schema should be rendered in DOCX.
 
 This allows you to preserve application-specific content in the exported Word file.
 
@@ -209,13 +209,13 @@ You can construct any supported `DOCX` elements in the `render` function using t
 
 <CodeDemo src="https://develop--tiptap-pro.netlify.app/preview/Extensions/ImportDocxCustomNode" />
 
-When importing a DOCX file, you can also define how custom nodes should be converted back to Tiptap nodes. This is done by passing an array of custom node definitions to the `import` command.
+When importing a DOCX file, you can also define how custom nodes should be converted back to Tiptap nodes. This is done by passing an array of custom node definitions to the `importDocx` command.
 
 ```ts
-import { Import } from '@tiptap-pro/extension-import'
+import { ImportDocx } from '@tiptap-pro/extension-import-docx'
 
 // ... inside your Editor or useEditor setup:
-Import.configure({
+ImportDocx.configure({
   appId: 'your-app-id',
   token: 'your-jwt',
   // ATTENTION: This is for demo purposes only
@@ -228,7 +228,7 @@ Import.configure({
 }),
 ```
 
-The latest version of the `@tiptap-pro/extension-import` has available the `promisemirrorNodes` configuration option. This option allows you to map custom nodes from the DOCX to your Tiptap schema. In the example above, we are mapping the `Hintbox` custom node from the DOCX to the `hintbox` custom node in our Tiptap schema. By doing so, whenever the DOCX contains a `Hintbox` custom node, it will be converted to a `hintbox` node in Tiptap when imported.
+The latest version of the `@tiptap-pro/extension-import-docx` has available the `promisemirrorNodes` configuration option. This option allows you to map custom nodes from the DOCX to your Tiptap schema. In the example above, we are mapping the `Hintbox` custom node from the DOCX to the `hintbox` custom node in our Tiptap schema. By doing so, whenever the DOCX contains a `Hintbox` custom node, it will be converted to a `hintbox` node in Tiptap when imported.
 
 <Callout title='DOCX, "prosemirrorNodes" and "prosemirrorMarks"' variant="info">
   Please note that the `promisemirrorNodes` and `prosemirrorMarks` options will only work if you're importing a `.docx` file. If you're importing another type of file, eg: an `.odt` file, the `/import` endpoint will be used instead of the `/import-docx` endpoint, and the `promisemirrorNodes` and `prosemirrorMarks` options will not be available, and therefore you'd need to rely on the [custom node and mark mapping API](/conversion/import-export/docx/rest-api#custom-node-and-mark-mapping) for those endpoints.

src/content/conversion/import-export/docx/preserve-images.mdx

@@ -23,12 +23,12 @@ This is a URL endpoint on your server that the conversion service will use to of
 
 ```js
  import { Editor } from '@tiptap/core'
- import { Import } from '@tiptap-pro/extension-import'
+ import { ImportDocx } from '@tiptap-pro/extension-import-docx'
 
  const editor = new Editor({
    // ... other editor options,
    extensions: [
-     Import.configure({
+     ImportDocx.configure({
        appId: '<your-app-id>',
        token: '<your-jwt>',
        imageUploadCallbackUrl: 'https://your-server.com/upload-image'