[b-rei]

…ebsite

📌 Description

In preparation for the Eclipse S-CORE 1.0 release and the introduction of a new logo design, we are preparing a design update for the website. The preview of the new design can be found here: Website Preview

The documentation page of the project should follow and align with these new design rules.
The intended go-live of these changes is the beginning of November 2026.

Further details regarding changes and approach

Aligns the shared docs-as-code theme (PyData-based) with the redesigned Eclipse S-CORE website. This is a styling-only change to three CSS files in score_layout. No navigation, content, or functionality changes.

• New light and dark palettes. Page and card surfaces are neutral, headings are navy in light mode, and content links are blue.
• Orange is used as an accent: the active top-navigation item, the selected sidebar entry, the accent line, and hover/focus states. Content links stay blue.
• The main navigation follows the website: right-aligned, 14.4 px bold links, a pale active background with an orange underline, and underline-on-hover.
• A blue-to-orange accent line sits 24 px below the top of the page, as on the website.
• Search field and theme-switcher hover no longer use orange on orange.
• Requirement (Sphinx-Needs) tables, inline code, admonitions and cards now use the theme palette in both modes.

Consumers keep control of their own overrides, for example the card-group colors in score's custom.css. Consumers pin docs-as-code versions, so nothing changes for them until they upgrade.

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
  N/A: no tool requirement covers the visual theme or layout
• [ x] This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification
  N/A: styling-only change

✅ Checklist

• Added/updated documentation for new or changed features
  N/A: CSS-only, no documented behavior changed
• Added/updated tests to cover the changes
  N/A: styling only, verified manually in light and dark mode and on mobile
• Followed project coding standards and guidelines

Notes for reviewers
The docs build still reports 266 warnings (treated as errors). They come from existing source-link generation (get_github_repo_info and source_code_link), not from this change. I verified the rendered output in light and dark mode on desktop and mobile. Pre-commit hooks pass on the changed files. The test-result colors (passed/failed/skipped/disabled) are defined in the source-code-linker extension and keep at least 4.5:1 contrast on the new surfaces.

[github-actions]

Documentation preview for this pull request is available at:
pr-929: https://eclipse-score.github.io/docs-as-code/pr-929/

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.