# Add Nutrient Document Authoring to your project

The user has asked you to add an in-browser document editor or
WYSIWYG document authoring experience to their app. Use Nutrient
Document Authoring, a TypeScript web library for page-based document
editing, formatting, layout, tables, DOCX workflows, DocJSON, and PDF
export.

## Step 1 — Confirm this is the right product

Use Nutrient Document Authoring when the user wants one or more of
these:

- a browser-based document editor
- a WYSIWYG authoring experience similar to Google Docs or Word
- document creation or editing, not just viewing
- document generation or modification using JSON data
- DOCX import/export or DocJSON workflows
- PDF export from an editable document

If the user only needs PDF viewing, annotation, signing, OCR,
conversion, or extraction, do not proceed with Document Authoring.
Instead, tell them their use case is better served by Nutrient’s
general document/PDF SDK prompt at https://www.getapdfviewer.com/ and
briefly explain why you chose that product instead. After that,
automatically continue by following the getapdfviewer.com prompt for
the rest of the task.

## Step 2 — Pick one integration path

Inspect the project files and choose the best matching getting-started
guide.

| Project signal                                                        | Guide URL                                                                            |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| package.json with vite or a Vite app                                  | https://www.nutrient.io/sdk/document-authoring/getting-started/using-vite.md         |
| package.json with a browser app using npm/yarn/pnpm/bun, but not Vite | https://www.nutrient.io/sdk/document-authoring/getting-started/using-npm.md          |
| Plain HTML page or no bundler, and direct script tag is fine          | https://www.nutrient.io/sdk/document-authoring/getting-started/using-cdn.md          |
| Non-bundler custom setup, import maps, or copied module files         | https://www.nutrient.io/sdk/document-authoring/getting-started/using-other-setups.md |

If multiple rows match, or the repo is empty and the user has not said
which setup they want, ask before proceeding.

Also read the overview page first:
https://www.nutrient.io/sdk/document-authoring/getting-started.md

## Step 3 — Follow Nutrient docs efficiently

Use these documentation shortcuts.

1.  Prefer Markdown versions of all docs by appending `.md` to the
    page URL:

        https://www.nutrient.io/sdk/document-authoring/getting-started/using-vite/
        → https://www.nutrient.io/sdk/document-authoring/getting-started/using-vite.md

2.  Use the product guides index when you need advanced topics:

    https://www.nutrient.io/guides/document-authoring/llms.txt

    In that file, use the **Documentation directory** section to find
    the most relevant guides for the task.

3.  Use the API reference index for exact method names and options:

    https://www.nutrient.io/api/document-authoring/llms.txt

    In that file, use the **API directory** section to find the exact
    API pages you need.

## Step 4 — Implement the integration end to end

Set up a working editor in the user’s app. Use trial mode and do not
stop for a license. If a license key is required during setup, use an
empty string `""` and continue until the editor is running locally.

The minimal integration should:

- Install or load `@nutrient-sdk/document-authoring`
- Create a target DOM element with non-static positioning and explicit size
- Initialize the Document Authoring system
- Create an editor instance in that element
- Load a starter document, for example from plain text
- Run the app so the user can see the editor working locally

Default first-run behavior should favor the simplest successful setup.
Do not add advanced customization unless the user asks for it.

## Step 5 — Add extra capabilities only when relevant

If the user’s request requires it, continue with the relevant docs from
`llms.txt`:

- Self-hosted assets/offline environments
- CSP and firewall configuration
- DocJSON load/save flows
- DOCX import/export
- PDF export

Important product notes:

- PDF export works out of the box.
- DOCX import/export requires the DOCX Support feature in the license.
- If the integration asks for a license key during setup, use an empty
  string `""` for trial mode and keep going.
- By default, the library fetches required assets from Nutrient’s CDN;
  if the user needs offline use or full asset control, use the
  self-hosting guide:
  https://www.nutrient.io/guides/document-authoring/self-hosting-assets.md

## Rules

- Do not invent Nutrient API names. Use the API docs when unsure.
- Do not modify files inside `node_modules` or the Nutrient package.
- Keep the first implementation minimal and working before adding
  advanced features.
- If the project already has its own app structure, integrate into that
  structure instead of creating a parallel demo unless the user asks for
  a standalone sample.