Hello,

If you have the time can you please post your answers to the folllowing questions, regarding a wiki based Inkscape manual?

1. What is the target audience?
2. The scope?
3. The depth?

Thank you,
vwanweb

I have a question for you...

Is it possible that you`re not aware of this Manual?
As far as I can tell, author of that manual is among Inkscape developers and most likely has the most proper insight on this matter. Also, wiki usually refers to a complete knowledge base about something where this existing manual only lacks some updates regarding the latest edition.

So, why would anybody go from the scratch where there is a firm ground to build upon?

Hello

I'd wish to know more what is the purpose of this inquiry. Based in Your previous messages, which I read quickly, You want to have a manual to share with Your students, which I think it's OK.

About Your questions, I think you are referring to http://wiki.inkscape.org/wiki/index.php/Inkscape?. I'm just another user. I have to say that, this last times I've tried to push my skills to developing my work around web, digital graphics and illustrations.

I'm saying this because I don't know if You are aware, of the kind of users that visit this forum, which is diverse in my opinion. Maybe better answers about the Inkscape Wiki can be found on the mailing lists, etc.

I will try to answer Your questions, the best I canN

1. What is the target audience?
For a Wiki, the ideal is any person. But not all the persons knows how to edit a wiki, and have time for it.

2. The scope?
It's all related to Inkscape. It also involves its development. It doesn't involve: The SVG format, Drawing and design concepts, other Graphic problems.
However It may involve the use of SVG files generated in Inkscape and the use of them in animations, web design, CAD/CAM design, etc.

3. The depth?
It's not the same than scope?... How depth can be that knowledge?... I imagine that even philosophic questions or scientific articles may be involved,.. like the use of Inkscape to visualize the distances between stars , ... or if a bezier curve drawn in Inkscape is only a point in other universe . But I think that wiki managers wont't allow that kind of editions last long.

I don't want to offend but ... Is this a kind of marketing strategy?? . I don't mind, but please let me know your purpose.

Regards

@Maestral: the licence, unfortunately, doesn't allow to edit Tav's manual. I've once exchanged a couple of mails about that subject with him and others, and the general direction was that we should either go with http://en.flossmanuals.net/inkscape/ (which already can be edited by anyone who creates an account and asks for access) or start from scratch.
There's also a very good introductory French manual that is currently being translated to English (written by Inkscape developer Nicolas Dufour and Documentation manager Elisa de Castro Guerra - but the website is offline atm., so a link doesn't make a lot of sense).

vwanweb knows all that already.

Hi Hulf2012
1. What is the target audience?
For a Wiki, the ideal is any person. But not all the persons knows how to edit a wiki, and have time for it.
Thank you.
One of the main drivers about creating a wiki-based approach to a manual is for ease of access to editing. The current FLOSS manual is based on data from 2008 and earlier, leaving the last 8-9 years of inkscape's latest features out of the documentation community. Wiki based would still have an administration level to it to avoid spoiler contributions, but the ease of access is very accelerated as international search engines direct traffic to wikis.

2. The scope?
It's all related to Inkscape. It also involves its development. It doesn't involve: The SVG format, Drawing and design concepts, other Graphic problems.
However It may involve the use of SVG files generated in Inkscape and the use of them in animations, web design, CAD/CAM design, etc.
Thank you


3. The depth?
It's not the same than scope?... How depth can be that knowledge?... I imagine that even philosophic questions or scientific articles may be involved,.. like the use of Inkscape to visualize the distances between stars , ... or if a bezier curve drawn in Inkscape is only a point in other universe . But I think that wiki managers wont't allow that kind of editions last long.
The difference between scope and depth, scope as an example will cover every Toolbox bar's tool, while the depth covers not only the toolbox bar's tools, but ensures examples of Arcs, Ellipses and Circles are explained in depth (step-by-step) for each mode of rendering. It would also go into details about the Tool Controls bar associated editing.

I don't want to offend but ... Is this a kind of marketing strategy?? . I don't mind, but please let me know your purpose.
The main purpose is to try and close the gap between the software release versions and supporting end user documentation. Currently there is not an up to date open source Inkscape v0.91 manual that a new user could read to become familiar with Inkscape's features. As for the marketing, millions of readers visit wikipedia and its sister domains on a daily basis. June of 2016 saw more than 7 billion views for the english wikis alone....
"While you read this, Wikipedia and its sister projects develop at a rate of over 10 edits per second, performed by editors from all over the world. Currently, the English Wikipedia includes 5,250,133 articles and it averages 800 new articles per day'." https://en.wikipedia.org/wiki/Wikipedia:Statistics

Thank you for taking the time to give me your feedback it is very appreciated.
-vwanweb

vwanweb wrote:The current FLOSS manual is based on data from 2008 and earlier, leaving the last 8-9 years of inkscape's latest features out of the documentation community.

The FLOSS manual could be brought up to date, by anyone who is motivated enough to do it.....or any group. It's much like a wiki, in that anyone who wants to, can register an account, and start editing. (as has been pointed out a few different times in this and other topics)

I'm curious why you want to create a wiki book, rather than contribute to the already existing FLOSS manual? They seem to be essentially the same type of format. What is the benefit of a wiki book, that the FLOSS manual doesn't share? (Or what is the negative thing about the FLOSS manual that the wiki book doesn't have?)