Update docs dark mode palette

[carlosabadia]

No description provided.

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing carlos/update-docs-colors (b26940d) with main (ed0cd15)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[greptile-apps]

Greptile Summary

This PR migrates the docs and marketing site from ad-hoc m-slate-*/c-slate-* color tokens to the unified secondary-* semantic palette and updates the dark mode slate scale to a darker base. The globals.css and custom-colors.css files in reflex-site-shared are deleted, consolidating all token definitions into the docs app's tailwind-theme.css and assets/custom-colors.css.

• Color token migration (61 files): Every slate-*, m-slate-*, c-slate-*, m-violet-*, and violet-* class or CSS variable reference is replaced with the corresponding secondary-* or primary-* semantic token.
• Dark palette update: The dark-mode --slate-1 through --slate-12 values are shifted darker to match the new design direction.
• CDN asset renames: Five SVG images have new filenames — these must be live on the CDN before the code change is deployed.

Confidence Score: 4/5

Safe to merge once the five renamed CDN assets are confirmed live — the code change itself is a straightforward token rename across CSS class strings.

The CDN asset renames will produce broken images if the new files are not already on the CDN at deploy time. Apart from that deployment dependency, the changes are purely cosmetic CSS class renames with no logic, data, or API impact.

ai_builder.py, hero.py, marketing_navbar.py, and cta_card.py all reference renamed CDN assets that must be uploaded before deployment.

Important Files Changed

Filename	Overview
docs/app/assets/custom-colors.css	Updates dark mode slate values to a darker palette and removes marketing color variables; file now lacks trailing newline.
docs/app/assets/tailwind-theme.css	Removes m-slate-* / m-violet-* Tailwind tokens and migrates component CSS references to secondary-*.
docs/app/reflex_docs/pages/docs_landing/views/ai_builder.py	Replaces m-slate-* tokens and renames two CDN SVG assets.
docs/app/reflex_docs/views/bottom_section/newsletter.py	Migrates most tokens but keeps focus:border-violet-9 instead of focus:border-primary-9.
docs/library/data-display/icon.md	Migrates color tokens but retains focus:border-violet-9 in the icon search input.
docs/app/reflex_docs/templates/docpage/docpage.py	Comprehensive migration from m-slate-/slate-/violet-* to secondary-/primary- across the doc page template.

Comments Outside Diff (1)

1. docs/app/reflex_docs/pages/docs_landing/views/ai_builder.py, line 1225-1235 (link)

   CDN asset renames need to be deployed before this PR goes live

   Five image URLs were renamed in this PR: getting_started.svg → getting_started_1.svg, mcp.svg → mcp_1.svg (here), squares_docs_logo.svg → squares_docs_logo_1.svg (hero.py), ship_navbar_3.svg → ship_navbar_4.svg (marketing_navbar.py), and cta_gray_lines_2.svg → cta_gray_lines_3.svg (cta_card.py). If these new files aren't already on the CDN at deploy time, all five will render as broken images. Please confirm the CDN has been updated before merging.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (3): Last reviewed commit: "Merge branch 'main' into carlos/update-d..." | Re-trigger Greptile}

[masenf]

looks the same to me running locally