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

New theme? #1182

Open
wants to merge 62 commits into
base: master
Choose a base branch
from
Open

New theme? #1182

wants to merge 62 commits into from

Conversation

antoinem
Copy link

Hello,

We’ve started a new theme derived from Darkfish.
You can see how it looks here:
https://basesecrete.github.io/rdoc/

As you can see, there are already quite a few changes (navigation, typography, colors, dark mode…).
We wanted to check if there was some interest, before we spend more time on it.

What do you think?

Cheers,
Antoine and Alexis

@st0012
Copy link
Member

st0012 commented Sep 30, 2024

Thank you for proposing this 🙌
I'm open to accept new optional themes and here's my thought on this topic:

  • To encourage more usage on this tool and documentation writing in Ruby in general, more theme options are needed (2~3 in rdoc may be the best?)
  • While whether rdoc maintainers will be able to maintain them long-term is surely a concern, I think it's a risk we need to take to grow the community. It can also be mitigated a bit through clear communication (e.g. we'll do our best but only the default theme is officially supported)

WDYT? @colby-swandale

A few notes to this PR:

  • Please submit document changes (e.g. update heading) in a separate PR
  • The addition of super_classes should be extracted too
  • Since it's a new theme, I think it's better to remove some references to darkfish like "Darkfish" Rdoc CSS.
  • I'm not familiar with js best practices, but my understanding is that darkfish.js unlikely to follow much of them. So I'd love to see new theme implementations not following its pattern unless necessary. I know it may be already on your roadmap, but I want to explicitly point it out.

alexisbernard added a commit to BaseSecrete/rdoc that referenced this pull request Sep 30, 2024
The purpose is to list all class ancestors in a new theme (see PR ruby#1182).
@alexisbernard
Copy link

Thanks for the feedback. I have extracted super_classes into its own PR.

I'm not familiar with js best practices, but my understanding is that darkfish.js unlikely to follow much of them. So I'd love to see new theme implementations not following its pattern unless necessary. I know it may be already on your roadmap, but I want to explicitly point it out.

We don't have specific plan for the JS. I think the less JS it contains, the better it is. We only added few lines of JS compared to Darkfish. Otherwise it could share the JS with Darkfish, but it would be more fragile.

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

Successfully merging this pull request may close these issues.

3 participants