-
Notifications
You must be signed in to change notification settings - Fork 17
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
Empty output .pd #13
Comments
Same problem on mac, it does not process correctly mkdocs.yml pages hierarchy. It produces a pandoc file with only the uppermost sections. |
Since a few months ago, MkDocs introduced the ability to write plugins, I'm going to adopt this code https://github.com/shauser/mkdocs-pdf-export-plugin to replace mkdocs-combine. MkDocs plugins give a much greater reliability that everything is really processed the way it should be. |
Thank you @twardoch ! |
Yeah, it needs to be adapted but it shows the principle well enough. I'll need to revisit it but if the code works as an MkDocs plugin then it'll have access to the same document tree as MkDocs proper, so combining it shouldn't be a problem. I still plan to just output one large Markdown file but it'll be more reliable, and possibly deal correctly with in-page links, something that the current code could never properly achieve. |
Hello,
I am using mkdocs and mkdocs-combine in a Windows Bash shell, everything works well for mkdocs serve and build, as well as mkdocs-combine pip installation with pandoc.
When i run mkdocs-combine i get an emtpy .pd file without any warning or notices.
Is there a way to have debug info?
Attached is the whole mkdocs project folder, consisting in a very minimal test site.
Thank you!
mydocs.zip
The text was updated successfully, but these errors were encountered: