📝 Document rich-text text color and add a rich-text troubleshooting page

[joshbermanssw]

cc: @tiagov8, @adamcogan, @kulesy, @18-th
Related PBI: tinacms/tinacms#7667

Summary

Text color in rich-text fields (tinacms#7683) has no docs, and it has edge cases where formatting breaks on reload (e.g. un**believ**able with "believ" colored reloads with literal **). This adds a Text Color section to the Rich-Text Fields page and a new Rich-Text Troubleshooting page, which also covers older rich-text gotchas (mid-word highlight in markdown fields, {} in MDX, Hugo stripping raw HTML).

Markdown (MD) Fields
├── Rich-Text Fields             + Text Color: palette, toolbar, saved output, rendering
│                                + textColors override; strikethrough/highlight/textColor in toolbar lists
└── Rich-Text Troubleshooting    new: text color + formatting and saving

Troubleshooting entries come from the round-trip tables in this #7667 comment. Acceptance criterion 8 (using it on the email-avoid-inline rule) is an SSW.Rules rollout task, not docs.

Merge after tinacms#7683 is released (and TinaCloud's @tinacms/graphql is bumped), so the docs don't describe a button nobody has yet.

Evidence

• pnpm tinacms build --local --skip-cloud-checks passes.
• Both pages parse with @tinacms/mdx with no invalid_markdown nodes.
• An Opus review checked every claim against the #7683 code; its findings are fixed.

Merge Danger

Door: two-way
Blast Radius: docs

The existing "Customize highlight colors" section documents a highlightColors override that no code reads; this PR leaves it alone.

Changes made by Claude Opus 5.5 via Claude Code.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 15, 2026 11:42pm UTC