Hi, IMHO, we need to provide an end-user documentation for 1.0. Many topics are regularly discussed in the list because they are not trivial to do with Viking.
To do this I encounter two main difficulties. The first one is technical: which document system should we use. I imagine we have to procide a file for the Gnome help system (at least). For the "source" of documentation I can imagine: - raw DocBook: directly supported by many tools from Gnome Doc Team - asciidoc (like Git): easy to read in its raw format, but I don't know if it could be integrated in the Gnome Doc process Any comment ? Any tips/experience to share ? The second one is related to documentation itself: what topics should be discussed in the doc? I imagine at least some non-evident actions like creating/expanding a track. What topic do you want to find in such documentation? -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
