Skip to content

docs(self-host): migration note leads with the already-deployed audience#185

Merged
tea-artist merged 1 commit into
mainfrom
docs-migration-pointer
Jul 17, 2026
Merged

docs(self-host): migration note leads with the already-deployed audience#185
tea-artist merged 1 commit into
mainfrom
docs-migration-pointer

Conversation

@tea-artist

Copy link
Copy Markdown
Contributor

The note under the Deployment comparison table framed migration as "start standalone today, add AI later" — aimed at people who haven't deployed yet. Its real audience is the opposite: people who already run Teable and want to upgrade. Rewritten (en/zh) to open with "Already running Teable?" and point straight at the repository's migration guide, with the three facts that matter up front: installs alongside, data stays in place, rollback = remove the added env vars.

The hidden standalone Docker guide's top banner gets the same split: starting fresh → full-featured platform; already running → migration guide.

🤖 Generated with Claude Code

… audience

The Deployment page note read as 'start standalone today, add AI later' —
but its real audience is people who already run Teable and want the full
platform. Rewrite it to say exactly that: already running Teable → follow
the repository's migration guide (runtime plane installs alongside, data
stays, rollback = remove the env vars). The hidden Docker guide's banner
gains the same pointer for its standalone readers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant