Le Sunday 15 June 2008 20:32:14 adam hyde, vous avez écrit : > hey, > > > - Do the chapters need to be a particular length (Adam)? > > Just jumping in to say that FM is really indexed towards thorough 'book > like' docs. this is because we output to online html, pdf, and books. > lots of short chapters dont really fit well into the index format we > have and don't output as easily into book form.
ok so 2 little chapter can be joined. (align and distribute AND objects transformed) But what is for you little chapter ? 3 pages is a little chapter ? For example a chapter dedicated at one tool is 2, 3 pages. introduction why to use how to use hotkeys tips Elisa > > adam > > > As for the issue of media, I think we should be concentrating on digital > > for the moment, getting something that makes sense for use online and > > download (including distribution with the software). I like the idea of > > using a simple type of chapter, though I could see a possibility to make > > use of sub-headings. However, I'm sure we can avoid them if we try hard > > ;) > > > > After quick glance at your list of chapters, it looks fairly complete > > and well-thought-out. Fortunately, we don't have to worry about > > organization at the moment, just getting all of the important content > > in, since we can organize it however we like later. > > > > I think if we can settle on a rough list of chapters soon, we can get > > some of the current content into them and start from there, thus saving > > a lot of work later that can be spent on other things. > > > > JF > > > > Elisa-yemanja wrote: > > > Hello all, > > > > > > I think it's time to speak about our futur work to made on booksprint. > > > It's better arrived and know a little about what exactly we will do. > > > > > > We know, it's for write an english manual of user for Inkscape. > > > If we can write a french manual, too, it's an side effect positiv, but > > > it's not more my goal. > > > > > > After, i can translate it. > > > > > > Fist of all, i thought we have already a TOC. > > > But with my little experience of author, i think this TOC, (very good > > > also) isn't perfect. > > > > > > Floss Manual advice : > > > * only use one Heading One (h1) for the chapter, at the top of the > > > page > > > > > > (and other : * bold technical terms when first used > > > * explain every step, and include clear screen shots for every step > > > * explain all jargon 'inline' > > > * make no references to chapters before or after ) > > > > > > Google need : 40 chapters > > > > > > One H1 for chapter => other organisation of the TOC. > > > Actually our official TOC have Part, H1, H2, H3.... > > > > > > Furthemore i have see, with the same content, the organization change > > > for each goal. > > > > > > What it make for me a little confusion is : > > > The main goal is write a paper book or an online manual ? > > > > > > For me the way to write change a little... Less details on online > > > manual. Short strings and not attention to construct a linear read. > > > Clic in internet is the king. Etc. > > > Print manual : organization of the chapter one after one ; why not > > > creat quick box (like "Be carful", or "HotKeys most used" etc ; I don't > > > know why, but paper editor love them. Maye it was for a good things. > > > Etc. > > > > > > Paper book or online manual, we can organize the same TOC, the same of > > > the kind of organization about our chapter. > > > > > > Here my proposal of a TOC. Be careful it was not "in order" (french > > > expression). It's a Twiki, so we don't care if we don't do chapter in > > > order. > > > > > > * = chapter > > > > > > * Interface and vocabulary > > > * Rectangle tool > > > * Circle tool > > > * Star tool > > > * 3Dbox tol > > > * Pen tool > > > * Bezier tool > > > * Calligraphic tool > > > * Layers > > > * Trace bitmap > > > * Menu Path > > > * LPE > > > * Text tool > > > * Gris, Guides, Snapping > > > * Ikscape and Wikimedia > > > * SVG > > > * Color and Style > > > * Pattern > > > * Tile Clone > > > * Spiral tool > > > * Node tool > > > * Selector tool > > > * Gradient tool > > > * Filters > > > * Eraser tool > > > * Exportation > > > * Importation > > > * Save > > > * Community > > > * Align and Distribute > > > * Personnaliser son Inkscape > > > * XML > > > * Propriétés du document > > > * Effects - color > > > * Effects - rendu > > > * Effects - Modifier le chemin > > > * Effects - Image Raster > > > * Effects - Visualisation du chemin > > > * Effets - Générer chemin > > > * Effects - Générer modèle > > > * Effects - Images > > > * Print > > > > > > Proposition of organization for each chapter : > > > * Chapter example of one tool > > > Introduction (why to use, purpose of this functionnality) > > > How to use > > > Hotkeys > > > Tips > > > > > > Other example : > > > * Color and Style > > > Introduction > > > Stroke > > > Fill > > > How to use > > > Markers > > > Creat his own markers > > > Hotkeys > > > Tips > > > > > > etc. I have already think in each organization of each chapter. But > > > this mail is very long. > > > > > > I can develop more after yours comments. > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Inkscape-docs mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/inkscape-docs -- Elisa ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Inkscape-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/inkscape-docs
