-
Notifications
You must be signed in to change notification settings - Fork 50
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
Link to generated PDF #271
Comments
should the PDF name include the lesson name, so that when it's downloaded it has a good name automatically? |
I would keep a generic name so that we can copy paste the workflow. The inconvenience for the client is minimal IMO. |
Now the link is https://coderefinery.github.io/documentation/lesson.pdf |
To change name: it can be configured in |
"Changing links in all the lessons is a bit annoying, though" - which links are these? We could provide a bash script that wgets and renames all. But I also don't mind if each has a unique pdf name. |
We plan to generate PDF as part of the Sphinx workflow. Let's not forget to link to the PDF from somewhere so that we find it.
It is currently called like this: https://coderefinery.github.io/documentation/_static/lesson.pdf
This does not exist yet at time of issue creation.
The text was updated successfully, but these errors were encountered: