Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDoc color scheme #1164

Open
colby-swandale opened this issue Aug 26, 2024 · 5 comments
Open

RDoc color scheme #1164

colby-swandale opened this issue Aug 26, 2024 · 5 comments

Comments

@colby-swandale
Copy link
Member

colby-swandale commented Aug 26, 2024

I think it's time to take a look at having something more friendly and accessible to the eyes. Let's use this ticket to capture some ideas and see if we can break some ground on putting a new set of colors together for RDoc.

Long live the green!

Notes

@st0012
Copy link
Member

st0012 commented Aug 27, 2024

We're also improving RDoc's development process (e.g. #1151). But before that's merged, you can use these steps to generate the documentation and see the changes:

  1. Run bundle install
  2. Run bundle exec rake
  3. Run bundle exec rdoc or bundle exec rake rdoc to generate the documentation

@adam12
Copy link
Contributor

adam12 commented Oct 30, 2024

Relaying some insights from discussions in Discord: the Lato font is incredibly thin and somewhat hard to read. Considerations for using system font stack instead?

@jaredcwhite
Copy link

Seconded…and even just adjusting the Lato font from weight 300 to normal 400 could help tremendously. This is a screenshot from my iPad, it's so hard for me to read. 🫣

image

@havenwood
Copy link

To me it seems even a bit hard to read than the screenshot on an iPad screen. Especially with grey, a thicker font would be much appreciated!

@st0012
Copy link
Member

st0012 commented Oct 30, 2024

Thanks for the feedback. I hope #1197 can address the issue 🙂

Also, I'd appreciate if you can open new issues for reporting different categories of problems as it'll 1) make them more searchable in the future, and 2) allow maintainers to close the issue once the problem has been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants