Add React support widget customization article

[Rieranthony]

Summary

• add article chore(deps): bump next from 15.3.2 to 15.3.3 in /packages/location #3 in the current content sequence focused on customizing a support widget in React
• explain the customization ladder from style overrides to custom triggers, composed content, and headless primitives
• sharpen positioning around code-first customization without making unsupported market-wide claims

Notes

• based only on repo/docs/shared strategy truth
• designed to follow and internally link from the existing React support widget setup article

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
facehash-landing	Ready	Preview, Comment	Mar 16, 2026 6:00am
web	Ready	Preview, Comment	Mar 16, 2026 6:00am

[greptile-apps]

Greptile Summary

Adds a new blog article (how-to-customize-a-support-widget-in-react.mdx) that walks through the customization ladder for the Cossistant React support widget — from classNames style overrides through custom triggers, composed content, and headless Primitives.

• The article is well-written, follows existing MDX patterns (uses Steps, Step, SignUpCTA components), and all code samples reference real @cossistant/react exports
• SEO metadata (title: 48 chars, description: 155 chars) is within the configured validation limits
• The related: [] frontmatter field is empty — it should link to how-to-add-a-support-widget-to-a-react-app since this article is explicitly designed as a follow-up
• The article body contains no internal links to the prerequisite setup article, despite the PR description stating it should "internally link from the existing React support widget setup article"

Confidence Score: 4/5

• This PR is safe to merge — it adds a single content-only MDX file with no code logic changes.
• Score of 4 reflects that this is a well-structured content addition with valid MDX components and SEO metadata, but has a gap between the PR description's stated intent (internal cross-linking) and the actual implementation (empty related field, no internal links).
• The related field in apps/web/content/blog/how-to-customize-a-support-widget-in-react.mdx should be populated, and the existing setup article may need a reciprocal update.

Important Files Changed

Filename	Overview
apps/web/content/blog/how-to-customize-a-support-widget-in-react.mdx	New blog article covering React support widget customization. Well-structured MDX with valid component usage and SEO metadata. Missing related cross-link to the setup article and no internal links back to the prerequisite setup guide despite the PR description stating it should link from the existing article.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Level 1: classNames\n(Style overrides)"] --> B["Level 2: Positioning Props\n(side, align, sideOffset)"]
    B --> C["Level 3: Support.Trigger\n(Custom chat bubble)"]
    C --> D["Level 4: Support.Content / Support.Root\n(Composed widget)"]
    D --> E["Level 5: Primitives API\n(Full headless control)"]

    style A fill:#e8f5e9
    style B fill:#c8e6c9
    style C fill:#a5d6a7
    style D fill:#81c784
    style E fill:#66bb6a

Loading

_{Last reviewed commit: 319ce70}