DOC-3356: New feature documentation for tinymceai.

[kemister85]

Ticket: DOC-3356

Revert reminder (temporary CI workaround)

• Revert commit 8121a0f7b5925f1c7631ac82442fb3ab98e19234 — After DOC-3399 is resolved or a permanent fix is in place, revert this commit so .github/workflows/preview_create.yml returns to the previous trigger set. This commit adds workflow_dispatch (manual preview when automatic runs fail), plus pull_request types edited and ready_for_review. edited also runs on PR title and body edits, which can enqueue extra workflow runs.

• Revert commit 20a10981fc27b1529071e7f81008c2b563cf3973 — Before merging this PR, revert this commit (or exclude it from the merge) so preview_create.yml is not changed on the target branch unless the team adopts the canonical redirects.json raw URL permanently. This commit switches the redirects input from .../refs/heads/main/redirects.json to .../main/redirects.json to unblock the docs preview workflow when the generate-redirects action cannot fetch the refs/heads URL.

Site: Staging branch

Changes:

TinyMCE AI documentation

• TinyMCE AI Introduction – Refined intro, AI service Cloud-only callout, and On-Premises section with contact link
• TinyMCE AI Overview
• Chat
• Review
• Actions
• API Overview
• API Quick Start
• Integration Options
• JWT Authentication Intro
• JWT with Node.js
• JWT with PHP
• Limits
• Models
• Permissions
• Privacy
• Streaming

Reference and configuration

• Available Menu Items
• Available Toolbar Buttons
• Editor Command Identifiers

Other affected pages

• 8.4.0 Release Notes
• Release Notes
• Changelog
• TinyDrive Getting Started
• Uploadcare Image

---

Pre-checks:

• Branch is correctly prefixed: feature/8.4.0/DOC-3356
• modules/ROOT/nav.adoc has been updated (if applicable).
• Files have been included where required (if applicable).
• Files removed have been deleted, not just excluded from the build (if applicable).
• Files added for New product features include a release note entry.
• Major or minor version changes have updated the supported-versions.adoc table.
• Build passes without console errors, warnings, or issues.

---

Review:

• Documentation Team Lead has reviewed.

[tiny-ben-tran]

May need to reword Write a script as the related section talks about Writing your own token endpoint. I also feel the steps are unclear and disconnected because there is no explanation for why creating and writing a token endpoint. And how can this be used in the plugin configuration?

[tiny-ben-tran]

If the next step is to go over theapi-overview the dev will be stuck in an infinite loop :). Looks like the next step should be to choose the right model?

[tiny-ben-tran]

All these links (ref to a streaming section in their respective page) has no useful info except for a link which takes back to this page

[soritaheng]

Suggested change

	|**Gemini 3 Pro**
	|Google's advanced model for versatile problem-solving and research
	|Yes
	|Yes
	|`'gemini-3-pro'`

There is no 'gemini-3-pro' in the available models' list.

[soritaheng]

Suggested change

	tinymceai_default_model: 'claude-3-5-haiku',
	tinymceai_default_model: 'claude-4-5-haiku',

This is the current model available

[soritaheng]

Suggested change

	The token endpoint will be requested:
	* At editor initialization
	* Periodically to refresh the token (typically every hour)
	The token endpoint will be requested:
	* At editor initialization
	* Periodically to refresh the token (typically every hour)

This is currently being rendered like this:

[kemister85]

One thing I noticed is that because we sort premium plugins alphabetically, old AI plugin is 3rd on the list, but the new one is almost at the end.

I have reused the signup component to feature tinymceai at the top of the premium plugins list. See this commit

[soritaheng]

Suggested change

	=== Writing your own token endpoint
	To create a custom security token endpoint, generate a keypair in the link:{accountjwturl}[JWT Keys] area of the Customer Portal. In the "Generate New Keypair" section, enter a description, select the key length, and click "Add Key". Alternatively, use "Import Public Key" to add an existing key.
	=== Writing your own token endpoint
	To create a custom security token endpoint, generate a keypair in the link:{accountjwturl}[JWT Keys] area of the Customer Portal. In the "Generate New Keypair" section, enter a description, select the key length, and click "Add Key". Alternatively, use "Import Public Key" to add an existing key.
	Once your keypair is created, use it to sign JWTs in your token endpoint. For step-by-step implementation instructions with complete code examples, see:
	* xref:tinymceai-with-jwt-authentication-nodejs.adoc[JWT authentication (Node.js)]: Complete Node.js implementation guide
	* xref:tinymceai-with-jwt-authentication-php.adoc[JWT authentication (PHP)]: Complete PHP implementation guide

There are additional steps after generating the keypair to set up the token endpoint. I think we could link to these two pages with the full instruction here like in the Quick setup