Skip to content

[Feature Request] Entrypoint to add additional themes ALONGSIDE the default (rather than overwriting/replacing them) #2048

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

Open
expikr opened this issue Mar 15, 2023 · 0 comments · May be fixed by #2059 or #2594
Labels
C-enhancement Category: Enhancement or feature request

Comments

@expikr
Copy link
Contributor

expikr commented Mar 15, 2023

Problem

According to the documentation, you either have to stick with the shipped themes or swap them out entirely/modifying them.

I would like to keep the default themes, but only add extra ones alongside them.

I would like to be able to easily make simple color alterations without having to go through the entire swamp of CSS.

I would like to be able to just find themes other people have shared and paste them into the direction and have it automatically show up in the dropdown selector of the compiled book

Proposed Solution

An entrypoint like Jekyll does with custom-variables would be neat, this way users don't need to deal with the entire CSS when all they want is a slightly altered color scheme.

Have the existing theme files be just a folder of stylesheets. Adding or removing them from the directory automatically changes the resulting dropdown listing to match what's in the folder.

Or perhaps something similar to SUMMARY.md but instead it's THEMES.md where you list out theme entries and their respective references.

Or some other ways of implementing that is ergonomic to the use case of "ok, it ships with these five themes, I want to remove two of the light ones, and add three of my own that is just a slight color tweak of Navy, without having to write an entire CSS sheet for every element"

Notes

No response

@expikr expikr added the C-enhancement Category: Enhancement or feature request label Mar 15, 2023
@expikr expikr linked a pull request Apr 9, 2023 that will close this issue
@tmandry tmandry linked a pull request Mar 14, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: Enhancement or feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant