[sf-perl] printable wiki

[Michael Friedman]

Adam,

If you can find a wiki with an automated TOC, then you can always create a printable view of any page by using custom CSS. Some wikis let you specify a CSS file to use and you can put special print-only markup in there that does things like strip off the headers and footers, sidebars, and navigation links. 

http://www.alistapart.com/articles/goingtoprint/
http://www.alistapart.com/articles/designingforcontext/

http://www.alistapart.com/articles/responsive-web-design/ (the "Meet the media query" section)

I've done this with an ancient UseMod Wiki with much success, but it doesn't have automated TOCs, so it probably wouldn't work for you.

-- Mike
______________________________________________________________________________
Mike Friedman | HighWire Press, Stanford Univ | friedman at highwire.stanford.edu

On Dec 2, 2010, at 11:49 PM, Peter Thoeny wrote:

> Hi Adam,
> 
> Yes, there are many wikis out there. Start at wikimatrix.org.
> 
> I can recommend TWiki wholeheartedly (totally unbiased! ;-)). Here is why:
> 
> 1. Create wiki pages that represent chapters of manuals, can be specific to departments.
> 
> 2. Define variables (macros) and use them in text. For example, if the product name is not set yet, define a BREADSLICER variable in the preferences and use it anywhere as %BREADSLICER%. You can change BREADSLICER at any time to reflect the actual product name.
> 
> 3. Create manual pages that include many chapter pages. Add a TOC to it to get an automated table of content. Example:
> 
> ---+!! Bread Slicer Manual
> %TOC%
> %INCLUDE{BreadSlicerChapter1}%
> %INCLUDE{BreadSlicerChapter2}%
> %INCLUDE{BreadSlicerChapter3}%
> %INCLUDE{BreadSlicerChapter4}%
> 
> 4. Install the FootNotePlugin if you need footnotes.
> 
> 5. Install the GenPDFAddOn that gives you a [ GDF ] button on every page. Use it to print the manuals. H1 headings start a new page.
> 
> BTW, we authored the Wikis for Dummies book using TWiki. We added a few more twists, such as automated outlines, an extraction app to correlate bits and pieces of interviews with specific chapters.
> 
> Hope this helps.
> 
> Regards,
> Peter
> 
> 
> On Dec 2, 2010, at 10:28 PM, Adam Masri wrote:
> 
>> Hello all,
>> 
>> Since I know we just had a talk on wikis...
>> 
>> At our printing business, I'm looking at using a wiki as a company-wide editable manual. Some dirty production areas of the business don't make sense to have computers around. So my goal is that I can easily print sections of the Wiki as a manual for specific departments.
>> 
>> Are any wikis particularly good for printing manuals, perhaps even with automated table of contents? Any pointers would be appreciated. There are a lot of them out there.
>> 
>> 
>> Adam Masri     masri at nolex.com
>> President      www.nolex.com
>> Nolex
>> 
>> _______________________________________________
>> SanFrancisco-pm mailing list
>> SanFrancisco-pm at pm.org
>> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm
> 
> -- 
>  * Peter Thoeny                             Peter[at]Thoeny.org
>  * http://twiki.net - Twiki, Inc. - Enterprise Agility
>  * http://twiki.org - is your team already TWiki enabled?
>  * Knowledge cannot be managed, it can be discovered and shared
>  * This e-mail is:   (_) private    (x) ask first    (_) public
> 
> 
> 
> 
> 
> 
> _______________________________________________
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm