-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Multi print page #108
base: master
Are you sure you want to change the base?
Multi print page #108
Conversation
…tion. Created get_toc_sidebar_section and modified get_html_from_items to detect use of a section before adding to the content.
I (finally) went through this PR. It indeed looks like working way to define multiple print pages for a given website. I am however concerned that this is adding a lot of additional logic (and an extra option) for what is a niche use-case that very few users will have. I also think the same can be achieved by splitting up your site into multiple smaller sites (that can each have a print page) using the projects plugin. In that case we could just write an instruction in the docs ( |
This adds the ability to define multiple pdfs by creating a dictionary of print_page settings with the key set to the print page name to generate. It uses the original configuration inputs as globals for print_pages unless the print page config overrides the setting. If print_pages is not defined within the mkdocs.yml then the configuration inputs add a single print_page item in the plugin print_pages.
This also resolves #76 by inspecting for the presence of child items within a section before adding to the TOC and Menu.