can you give concrete examples on this?
I didn't record the many problems we faced when trying to get started. Once you know and understand the 'why' many of these things are obvious, but we had many times where we questioned using ABP in the beginning. The best way to identify these things would be to watch someone starting out using ABP for the first time (don't help them, just document where they have challenges). You will find a number of barriers to startup which can be solved with a little bit more detail in the documentation.
Using a tiered architecture, separate identity server, and Docker all added to the places where we had problems. Again, the problems were our own, but they were with things we expected to be solved by ABP (and they were, but you have to get the configuration correct, and we were using ABP because we may not have deep experience in all of the areas...).
We have found MANY times that the documentation DOES contain the answers to problems we face, but the information is not presented in a way that is obvious to people who are new to ABP. One suggestion for improving the help would be to select a mid-level developer who has NO experience with ABP, and observe them (without helping) as they try to create a new project (do this do a different person for each 'type' of project). Document the things that cause problems and highlight those things better in the documentation. A related improvement would be to explain WHY certain things are done the way they are - once you understand the framework this becomes obvious, but when starting out many things can seem overly complicated when you do not understand why.