-
Notifications
You must be signed in to change notification settings - Fork 440
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
base: master
Are you sure you want to change the base?
New theme? #1182
Conversation
Thank you for proposing this 🙌
WDYT? @colby-swandale A few notes to this PR:
|
The purpose is to list all class ancestors in a new theme (see PR ruby#1182).
Thanks for the feedback. I have extracted
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. |
This template ticks several boxes of things people would like to see in darkhorse, particularly Table of Contents navigation & Dark Mode, the new Rails documentation site shows this off well. Introducing a new HTML template would add quite a significant load to maintain, so I would more like to see us pluck these features into darkhorse. |
I've deleted the new theme folder and copied the changes in the darkfish theme folder. |
@@ -1,23 +1,19 @@ | |||
<body id="top" role="document" class="file"> | |||
<%= render '_sidebar_toggle.rhtml' %> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we changing darkfish templates too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Colby said:
so I would more like to see us pluck these features into darkhorse.
So I deleted the new theme folder and modified the Darkfish templates.
Here, the sidebar toggle is rendered in the new topbar partial.
I would have preferred to keep it separated and fine-tune it until it eventually becomes the new default theme, but I understand adding a new theme would require more maintenance.
How would you like us to proceed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I missed that comment. I strongly prefer having it as a new theme and maintain it in parallel at least for a while.
But given that Colby and I have contrary opinions now, I'd advise you to hold off any future changes until we reached an agreement 🙏
@colby-swandale It's darkfish, not darkhorse 🙂 |
IMHO good idea to keep it separate as well for some time and switch defaults at some point with major bump or so. |
Apologies, my suggestion has gotten lost in translation I think. I wasn't suggesting that the entire Darkfish template be replaced, Instead I was suggesting plucking specific features from this Pull Requests into new PRs that can be added to darkfish like Table of Contents, Dark mode etc. Of course any new changes to Darkfish will need to consider the existing theme and make suitable adjustments. |
+1 This is IMHO a significant improvement over the status quo. Thanks a lot for your work! |
We moved the theme into it's own gem (https://github.com/BaseSecrete/rorvswild-theme-rdoc), so anyone can use it without waiting for merging. If you would like to have it directly into RDoc, we will be very happy to update the PR. |
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