StabilityNexus / StabilityNexus/Windmill-EVM-WebUI
[FEATURE]: Improve text contrast and readability across the dark theme, especially for body text and secondary content in documentation pages.
@Jayesh-git10 is already working on this.
Since Sep 19, 2026.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 14
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 22
Description
Feature and its Use Cases
Currently, some body text appears very dark gray against the dark background, making it difficult to read. The feature would introduce a more readable text color while maintaining the existing visual hierarchy between headings, body text, and muted content.
Use Cases
- Improve readability of documentation and informational pages.
- Make paragraphs and descriptions easier to read in dark mode.
- Improve accessibility by providing better contrast between text and the background.
- Maintain consistent typography and text contrast across different sections of the application.
Additional Context
The issue can be observed in multiple documentation sections, including:
- Strategy descriptions
- Configuration Reference tables
- Buy/Sell order descriptions
- Price Bounds
- Settlement Price
Headings have sufficient contrast, but the accompanying body text appears significantly darker and is harder to read.
The proposed change should preferably use the existing theme/design tokens so that the improvement is applied consistently rather than changing individual components separately.
Screenshots demonstrating the current contrast issue are attached.
See the dark grey text against the black background. It has low contrast, which makes the content difficult to read. It would be better to use a lighter shade for the body text and other necessary sections to improve readability while maintaining the existing visual hierarchy.
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.