Some people ask for downloadable versions of some handbookpages, expecially the cookbook
So i created just the pdf out of http://drupal.org/book/export/html/120612
It is worth to add to the handbook page?
| Comment | File | Size | Author |
|---|---|---|---|
| cookbook.pdf | 642.87 KB | dawehner |
Comments
Comment #1
add1sun commentedSure thing. When you add it, please make sure it is clear at what date the PDF was created. Since the handbook changes all the time the contents of the PDF will be slightly different from the HTML pages.
Comment #2
xamountDownload links looks good....but are we going to keep updating the pdf download link every time someone edits the handbook page?
Comment #3
HansBKK commentedLOL
As someone who does actually try to keep up with http://drupal.org/handbook/updates
I think monthly would be good though - who wants to volunteer?
Comment #4
xamounterr...I think having volunteers for this would be setting a bad precedence....but that's just my 2 cents..
Comment #5
HansBKK commentedxamount, do you mean you think a paid staffer should do it? Employed by whom?
or do you just mean a random noob might mess it up?
I'm not arguing, just trying to understand your meaning. . .
Comment #6
add1sun commentedActually I think the best thing would be to have a page that explains how to make your own copy of the handbook pages (printing to PDF or whatever other format they want) and refer to that page at the start of significant books or sections. That way people learn something useful AND get an up to date copy of the document and it is one fewer thing for us to monkey with.
Comment #7
leehunter commentedIs there anything in the plans for the redesign to automate PDF files? Maybe a cron job that generates a new version of each handbook every day and provides a link.
Comment #8
add1sun commentedNot that I'm aware of at this point.
Comment #9
xamountbetter yet, having a cron job that generates a new pdf link ONLY when the handbook is updated....or maybe a hook into nodeapi on op = update?
Comment #10
HansBKK commentedxamount, you may not realize it, but if you check the link I posted, the handbook gets updated sometimes every five minutes, would be a waste of server resources.
+1 to Addi's scratch your own itch solution.
Comment #11
xamountSorry, i should have said when the handbook PAGE is updated, just generate a new pdf link for THAT handbook page. I doubt one handbook page will be updated every 5 mins.....right?
Comment #12
HansBKK commentedxamount, I'm not following, are you saying you want a separate PDF download available for each and every node in the handbook??
Comment #13
xamountWell that's what we are discussing right now (as per the title of this issue...ie a "PDF download available for each and every node in the handbook").
I'm not saying a pdf version of every single node on drupal.org but if that's a popular request by ends users....well I say give it to them. If its too much server resources, then maybe as add1sun says, we can do up a tutorial page explaining how to create a pdf version on the fly.
Comment #14
HansBKK commentedSo far AFAIC the discussion has been creating PDF of "the cookbook", which is a whole collection of nodes.
Why would you ever want a PDF of a single node?
And if you really do, then just create it yourself from your desktop when you need it, there are lots of tools that can do this.
IMO this is exactly like asking drupal.org to put a "print this" button on every page.
Comment #15
xamountAhh sorry, think I confused the terms handbook and cookbook. Yes, +1 for add1sun's suggestion.
Comment #16
add1sun commentedThis page explaining how to make an offline copy already exists. http://drupal.org/node/472396 So, if folks want to add a link to doc pages, feel free, though I think it would be good to have it be a "help" link that appears on all handbook pages somewhere in the redesign. Moving this to a request for the redesign.
Comment #17
arianek commentedLooks like the current printer friendly pages link and the instructions linked to in the previous comment are pretty straightforward. I'm going to close this (feel free to reopen if you think otherwise!)