Skip to content

Apply brand tone and writing style fixes #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Apply brand tone and writing style fixes #267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion async-collaboration/comments/setup/apryse.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ npm i @pdftron/webviewer

**Serve Apryse's runtime assets**

Apryse's WebViewer isn't just JavaScript — it ships with a **WebAssembly core**, the **Office Editor engine**, and a **UI shell** (HTML/CSS/JS), all under `node_modules/@pdftron/webviewer/public/`. These are loaded at runtime over **HTTP** from a URL on your site (the `path` option you pass to `WebViewer(...)`), *not* via a JS import — so your bundler won't pick them up on its own. You need to copy them into your app's static folder so the browser can fetch them.
Apryse's WebViewer isn't just JavaScript — it ships with a **WebAssembly core**, the **Office Editor engine**, and a **UI shell** (HTML/CSS/JS), all under `node_modules/@pdftron/webviewer/public/`. The browser loads these at runtime over **HTTP** from a URL on your site (the `path` option you pass to `WebViewer(...)`), *not* via a JS import. Your bundler won't pick them up on its own, so you need to copy them into your app's static folder so the browser can fetch them.

Most teams automate this with a `postinstall` script:

Expand Down
2 changes: 1 addition & 1 deletion async-collaboration/comments/setup/lexical.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ npm install @veltdev/lexical-velt-comments @veltdev/client lexical
</Tab>
</Tabs>

#### Step 7: Persist Editor Content Without Velt Marks (optional)
#### Step 7: Persist editor content without Velt marks (optional)

- When saving editor content to your backend, you may want to exclude Velt comment marks to keep the content clean.
- Use `exportJSONWithoutComments` to export the editor state as JSON without Velt comment nodes.
Expand Down
2 changes: 1 addition & 1 deletion async-collaboration/comments/setup/slatejs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ npm i @veltdev/slate-velt-comments
</Tab>
</Tabs>

#### Step 4: Register Velt Component Type in SlateJS
#### Step 4: Register Velt component type in SlateJS

- Register the Velt Comments Element type with your SlateJS editor's custom types.
- This ensures proper type checking for the comments functionality.
Expand Down