On 02/08/10 09:07, Karsten Wade wrote: > On Fri, Jul 30, 2010 at 08:40:44PM -0400, Christopher R. Antila wrote: ... > This scheme gives two types of documentation: a fixed release guide > that can be printed and referenced; a more flowing set of wiki pages > with various quantities and qualities of information. Is this scheme already used in other fields of Fedora ? Anyway, makes a lot of sense: developer (writers) just commit fixes/changes to the wiki whenever they can and the (print) manual gets updated with information as needed. I do find that long wiki pages can be overwhelming to use. You see it load, and the web browser vertical scroll bar pointer ends up tiny. You scroll a few pages down, and realize that you simply don't have the time to read that much, and try finding alternate material. For a music spin, is there an easy process to extract the contents of the wiki pages so that they can be added as ?html? to a spin. (eg assume user doesn't have internet where they are using the spin) ? _______________________________________________ music mailing list music@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/music
