Skip to content

style(docs): complete neutral palette across hard-coded UI colors - #70

Merged
NathanNeurotic merged 6 commits into
masterfrom
style/complete-neutral-palette-20261114
Nov 14, 2026
Merged

NathanNeurotic merged 6 commits into
masterfrom
style/complete-neutral-palette-20261114

Conversation

@NathanNeurotic

@NathanNeurotic NathanNeurotic commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Problem

The first monochrome pass changed root palette variables but left hard-coded blue/purple colors in individual UI elements. The sites therefore still looked inconsistent.

Changes

  • Replace remaining cool-toned literal colors in the site CSS with neutral gray equivalents to align panels, cards, borders, text, decorative glows, and hover backgrounds.
  • Preserve the existing CSS variables, document content, JavaScript, images, status/warning colors and PlayStation controller symbols.
  • Do not change layouts or markup.
  • Update both the maintained site stylesheet and the checked-in documentation output, keeping them identical.

Safety

Draft pending desktop/mobile visual review and applicable CI; no merge or deploy from this PR until validated.

Attribution

The site footer displays Color scheme by gamerman 5000. It is installed through the shared site script or maintained generator/layout to survive normal documentation builds.

Additional fixes

Page-specific blue surfaces were aligned on the fork-gap audit pages (RiptOPL/Open-PS2-Loader) and in the SMS-specific stylesheet (Simple-Media-System). The PlayStation symbols, semantic status colors and artwork remain project-specific.

Rollout

The user authorized merge-and-visual-check with a revert if necessary. Confirm CI and changed file scope before merging.

Summary by CodeRabbit

  • New Features
    • Documentation pages now display a footer credit for the color scheme, when a footer is present and no credit already exists.
  • Style
    • Updated documentation theme colors to use charcoal backgrounds and neutral gray accents. PlayStation button and status colors remain distinct.
    • Updated supporting page elements, including links, focus outlines, tags, the release strip, table of contents, and mobile sidebar, to use the shared theme colors.

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Explain Change →

Caution

Review failed

The pull request is closed.

Walkthrough

The documentation assets replace many blue-toned styles with charcoal and neutral grays, and update SMS styles to use shared theme variables. Both documentation app scripts add a contributor attribution to the footer when a footer exists and the attribution is not already present.

Changes: Documentation theme styling

Layer / File(s) Summary
Theme colors and core content
docs/assets/style.css, docs-site/static/assets/style.css, docs/assets/sms.css, docs-site/static/assets/sms.css
Core text, navigation, search, content, and table styles use neutral colors. SMS styles use shared theme variables for several elements and remove the --ink3 declaration.
Glossary, hero, and credits
docs/assets/style.css, docs-site/static/assets/style.css
Glossary, hero, credits, and telemetry styles use charcoal and neutral grays. Responsive behavior remains unchanged.
Component surfaces and controls
docs/assets/style.css, docs-site/static/assets/style.css
Buttons, cards, callouts, downloads, alerts, pathways, and related styles use charcoal and neutral grays. Existing interactions and status colors remain in place.

Footer attribution

Layer / File(s) Summary
Conditional footer attribution
docs/assets/app.js, docs-site/static/assets/app.js
Each script appends a contributor attribution paragraph when a footer exists and no .color-scheme-credit element is present.

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Other

Merge Risk: Low · up to 8a425

This restyle replaces blue tones with neutral grays. The one known issue is that small labels in the responsive credits table become slightly hard to read when hovered. It is a low-impact, easily fixed gap that should be addressed or accepted before merge, along with the pending visual review.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@NathanNeurotic
NathanNeurotic marked this pull request as ready for review November 14, 2026 16:14
@NathanNeurotic
NathanNeurotic merged commit e65ced3 into master Nov 14, 2026
8 of 9 checks passed
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