I would like to work on the following aspects. How do we approach this?
Coverage. A lot of questions from the forum could be answered with in the official manual. Either the information is missing or can not be found. (In a Information Architecture sense, not in a technical search engine way.)
Assumptions. Neos features some unique concepts. New users are faced to grasp them efficiently. (Mapping content to nodes, properties, using fusion, eel, flow...) The current manual expects users to be familiar with certain concepts. (Example: If you're used to WordPress and now are learning or even looking at Neos you will not understand how to build your website. If you're coming from TYPO3 Fusion will be a natural progression.)
General organisation. Documentation is divided per package. This is a legitimate structure but as a user that installs the "whole CMS" there is only one package: Neos. Either we find a way to guide a user through the individual package docs or we unify them. Possibly just rendering all those single repositories under one domain as separate chapters...
This is an intentional cross posting from GitHub Issue #1771
I would like to hear your input on my pressure points and on what tooling to use for coordination.