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

As a user, I would like instructions on to edit the themes #66

Open
EricPonvelle opened this issue Jun 10, 2020 · 4 comments
Open

As a user, I would like instructions on to edit the themes #66

EricPonvelle opened this issue Jun 10, 2020 · 4 comments

Comments

@EricPonvelle
Copy link

Hello,

I really liked the themes, and my company was looking at using these styles to do some proof-of-concept documentation before we can convert everything to this standard. However, as usual, people were questioning the colors. Go figure.

I was curious if I could get an explanation with how to change the themes colors and such. I have an extra-css file that Id like to use to keep everything easy for the rest of the team.

If I can get some insight, I would also like to contribute my experiences and a guide to the Wiki on here.

@fu-sen
Copy link

fu-sen commented Mar 22, 2021

This is in the MkDocs documentation:
https://www.mkdocs.org/user-guide/configuration/#extra_css

@EricPonvelle
Copy link
Author

That is the link of how to structure the directory with .css files. I wanted to see the names of elements to change the stock themes to meet our needs.

@fu-sen
Copy link

fu-sen commented Mar 25, 2021

The theme is set in theme of mkdocs.yml. Is there a way to change this?

mkdocs.yml:

theme:
    name: flatly

Only the CSS for that theme goes into the site/ directory. Not all theme .css are included.
Therefore, some means is required to achieve it.

@fu-sen
Copy link

fu-sen commented Mar 25, 2021

I think this is what you want to achieve:
http://strapdown.ztx.io/

This GitHub Project may give you a hint to make it happen:
https://github.com/chaitin/strapdown-zeta

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

No branches or pull requests

2 participants