Michael Howard

Looks clear and organized.

Dimitry, understand. I am able to access the gitbook space you created.

Pedro, Absolutely! Human translators are essential. I've tried to use several translation software tools on the excellent Spanish Freeplane manual by Luis Javier González Caballero. Horrible results especially trying to maintain the structure and links! Does anyone have an idea for a universal structure (table of contents, numbering, etc.) that allows the human translators to focus on grammar nuances without spending hours on format? I think the question/answer format is familiar to most users regardless...

I just signed up on Github and will spend some time learning the basic features. I think most FP users will use Sourceforge just to point out perceived deficiencies in the software, request new features or documentation. Only a few will agree to write detailed documentation. We'll probably need to draft the content (on Github) and ask them if it fills the need via a reply to the OP (on Sourceforge). Simply attach the draft to the response. So very few people will need access to Github. Maybe just...

I agree with your assessment. I think it would be helpful to clean the tickets out. Are the tickets useful to the coders or just another box to check?

Great Idea! The SourceForge Wiki has the capability to create lists and well formatted documents. Of course, FP itself can self-document. If we need a more structured documents we can use LibreOffice and post the products as PDF. I've done several website/information repositories and this approach works well.

Of course good documentation is much more than a FAQ page. However, an FAQ page serves an important role in the development of deeper content. I agree that beginners don't know what questions to ask. That's why FAQ lists were created. How about an FAQ explaining mind-mapping? An FAQ is simply a structured way to present important concepts to the users. Also a great quick way to organize existing data from forums and "requested features" and "documentation". As a new FP user, I need specific bite...

I'm glad we're not rushing to a "solution". I think everything you both offer is really useful. We can gather existing information for a FAQ type page on the wiki while stripping out the outdated or incorrect data. Each FAQ can include the question and then a brief answer. If needed, a more in-depth answer/tutorial can be linked from the FAQ. I can develop an FAQ page if you think it's a good idea.