Well, now I think Lukas should say anything. On the one hand the information and the infrastructure is there.
www.piercms.com is a wiki, right? :) So we are talking again where to put information and how to collaborate. I only had the impression that the book form of the wiki might concentrate the efforts better.
Lukas, is
www.piercms.com open for content contributors? Do you think a book is a good idea or do you have the impression that the wiki pages are sufficient for documenting?
As Lukas is not
speaking up I assume he is not interested.
Well, he probably knows how time consuming may be such a project ;-)
Also, he has already written quite a lot on this topic.
What's there really new to add?
Well, as long as there are questions about pier there is something to add. I think newbie information is rare. There are a lot of things doable with default pier. These things depend often on the difference between linking, embedding and the available parameters. Other use cases are solvable with permissions (and/or embedding things). I know no information source that explains PRDocument and possible usage and this is quite a powerful feature. That is only usage. The more you work with pier the more you want to extend it. Information about the class hierarchies is not really there. E.g. how to embed a widget programmatically in a page. How to write a command? Why and how to extend PRValueLink?. ......