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.

Sign up for GitHub

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

Jump to bottom

Feature request: allow for a single style sheet #79

Open
annevk opened this issue Jan 11, 2018 · 4 comments
Open

Feature request: allow for a single style sheet #79

annevk opened this issue Jan 11, 2018 · 4 comments
Assignees
@aperezdc
Labels
enhancement good first bug
Milestone
v0.4.4

Comments

@annevk
Copy link

annevk commented Jan 11, 2018

It would be nice if we could disable the builtin style sheet altogether.
@annevk annevk mentioned this issue Jan 11, 2018
Merged
@annevk
Copy link
Author

annevk commented Jan 11, 2018

An alternative solution might be to give more control over the template that produces the HTML. That way we could also use <!doctype html> and simplify a few other things.

@aperezdc
Copy link
Owner

I am afraid that disabling the built-in CSS implicitly when a custom one is specified with fancyindex_css_href might break existing setups. Would it be acceptable for your you to have an additional configuration directive which disables the built-in CSS?

Regarding the additional customization, is there something in particular that you need which fancyindex_header does not cover? A concrete example would help me understand better.

@annevk
Copy link
Author

annevk commented Jan 18, 2018

Heya, thanks for the reply. An additional directive would be great.

As for templating, what I'd like to be able to do is make the markup of https://n.whatwg.org/ more similar to that of https://whatwg.org/. In particular, adjust the doctype, adjust meta viewport, add meta theme-color, add link icon, and such. So they make for a more coherent whole.

@aperezdc aperezdc self-assigned this Jan 18, 2018
@aperezdc aperezdc added this to the v0.4.3 milestone Jan 18, 2018
@domenic
Copy link

domenic commented Jan 18, 2018

Note that the doctype was fixed recently in a3a7626, so we probably just need to update our installation for that part.

@aperezdc aperezdc modified the milestones: v0.4.3, v0.4.4 Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aperezdc aperezdc

Labels
enhancement good first bug
Projects
None yet
Milestone
v0.4.4
Development

No branches or pull requests
3 participants
@domenic @aperezdc @annevk