Why did you think I didn’t like something in that link? I am talking about something completely different.
You pointed to the documentfoundation.org wiki, which is separate; and changing it is fine and great - but absolutely unrelated to making a post here, on Discourse, a wiki post.
Let me go ahead and try that, to see what would happen.
Yes, I misunderstood that, sorry. 
Another wiki, pfhh.
Suggested addition to the FAQ: Could you mention explicitly (not indirectly) that the site uses the Discourse engine? Also there is other useful information in Where is the help on using Discourse, that is easily discoverable by users?.
No, I can’t, as far as I know only an admin can the FAQ edit.
I will address 
@guilhem here, maybe he can help.
The guide needs a ToC, where one may see the structure of the guide, and navigate to the interesting topics easily. Otherwise, e.g. users won’t ever scroll down to the “what’s appropriate here” section, even if they happen to open the page.
Why not simply importing the content into About the English category? There is also Guidelines for asking. I believe pinned topics such as these would have more visibility compared to pages on external sites.
@guilhem , thank you for your reply.
There is also Guidelines for asking. I believe pinned topics such as these would have more visibility compared to pages on external sites.
I looked at the links you mentioned and to me they don’t seem suitable.
If you really wanted to open a topic, IMHO it should be called “How to use the Ask page”.
After all, the point is to describe the individual options for this page and for Q&A and to supplement them with pictures.
Why not simply importing the content into About the English category?
Simply importing the content into About the English category is not a solution, because the old Ask page is described on the wiki page and is no longer valid due to the new features.
Basically the description has to be recreated, no matter if on the wiki page or here.
I believe pinned topics such as these would have more visibility…
I have great respect for your believe.
However, the question I have is, How can the new description to be created always be accessed from the same starting point?
I would like to briefly describe what I consider to be the advantage of a wiki page:
My summary: Not everything new is better, but you can work on it.
At the moment I don’t see any sense in adding a description to a question/answer structure.
Thanks again to all who have sacrificed their time so far.
I fail to see how that’s an argument against any particular solution; retitling and editing is a no brainer both here as well as on the wiki.
Sure, didn’t mean to import verbatim…
Not sure what do you mean here? Wiki pages and Discourse topics are both accessible directly by their respective URLs, and these URLs can be linked in the FAQ, any other topics, the footer, wherever. One does not exclude the other. In addition though, pinned Discourse topics will show up at the top of the list until read/unlisted; internal links can be automatically prettified and scored; and consolidating links within a single site means more visibility in terms of SEO.
FWIW AskBot sent very few people to that wiki page: during the week-preceeding the migration I count only 7 requests… The reality is probably a bit higher since not everyone sends the referrer across origins, but even when counting all requests minus the ones that are obviously bots I count only 20 under the same period; and most of these originate from individual Askbot questions such as Inkscape and Libreoffice. Not saying moving it elsewhere will magically raise awareness, but there is room for improvement 
That’s true, but I’m not sure how important that is in that context — Cc’ing @sophi for her advice. AFAIK folks on the localized sites/categories have different workflow and etiquette, not everything has to be aligned to English.
I guess opinions diverge about it even among prominent Askbot users, see for instance Guidelines for asking I’m not really an AskLibO user myself, but noticed that there is already a lot of content here that’s not suitable for a QnA workflow, starting with this very topic or #meta in general. Unlike before we can now disable QnA for particular categories and/or tags for a typical forum-like experience. We can also auto-delete replies and auto-close topics after a configurable period. And pin topics to bring them to users’ attention and increase visibility.
Some ideas to improve visibility:
No idea how hard it would be to implement these, but in principle it should be doable.
@guilhem thank you very much for your explanations and reasons.
I don’t want to go into all the points directly now, but bring the concern to the front.
One point that has not been a priority for me so far has convinced me to use the AskLibO.
It is the possibility that all users can contribute to this description. This would be a bit more difficult with the wiki.
I am convinced that you will find a good solution for the visibility (link, pin or similar).
As title I would like to use the already mentioned “How to use the Ask page”.
If someone has a better suggestion for this, it can be named here.
I will create a rough content and post it here (at: How to use the Ask page) (in a few days).
To get a certain structure for the whole thing, I imagine to use the actual question to write an introduction.
Individual answers should then stand for the individual function points.
Just an example:
Question: Introduction / Basics
Answer 1: Function 1
Answer 2: Function 2
etc.
Are there any other suggestions for the structure?
Nice work, looks great to me! But as said I’m not really the right person to review this because I’m not really using AskLibO in the first place OTOH your fellow TL4 users will probably be able to give valuable feedback.
The only thing that pops to mind is, I thought you’d be re-using About the English category. That post was (automatically) created for this very purpose and meant to be edited with proper content by community members. Perhaps your new topic could be merged in? It’s not that we have to use this post, but if not then I guess it should be un-pined and deleted. Or did you have another purpose in mind for that topic?
Either way, should I toggle QnA on your topic? Right now it shows with a couple of Answers which are not really answers/solutions per se Without QnA they’ll show are mere replies instead, with any follow-up replies being added at the end.
Either way, should I toggle QnA on your topic?
Yes, that’s a good idea. 
I don’t think I understand enough about it
As it turns out it’s not possible to toggle it on a per-topic basis. The only exception is the so-called category topic which is About the English category . I suppose that’s a strong reason to reuse that topic instead of creating a new one It’s possible to disable QnA for specific tags though.
@guilhem , sorry for the Question.
Is the topic allocation of
done, or is there still something that needs to be done?
In the meantime, I have additionally created the topic in the wiki.
https://wiki.documentfoundation.org/Ask/Guide_-_How_to_use_the_Ask_site
It is also already localized for German.
For hints in answers it is easier to handle, because you can also jump to a sublink.
Not sure what you mean by “Topic allocation”, but if you don’t want to recycle the category “landing page” About the English category and is fine with QnA presentation then I guess it is. The landing page ought to be deleted or filled some some other content though.
It’s also doable here, you can jump to a particular by appending its number (see the 
icon at the footer), and each heading is assigned an anchor, too (hover to see the link). For instance
It’s also doable here, …
Ah, thanks.
@guilhem
in About the English category is written: “(Replace this first paragraph…”.
Is this what the title means. (Sorry I am not a native English speaker)
The topic title? No, that’s ”About the English category” and you can edit it by clicking on the pencil next to it. You might need to add a tag, in that case #meta is probably a good choice since we’ll need to recategorize/review these anyway.