I've been trying for quite a long time now to understand the structure of ds/lib. I've read the FAQ where it explains what's in every directory, which has helped some. I've read all several times, but the intermediate LPC docs, and I feel that some kind of structural explanation would really be clarifying for many people.
I think that a simple explanation of the ds filesystem would be great, what were the intentions behind the structure of the library (like the structure of UNIX and Windows filesystems). That way we could know, for example, what's the difference between include and secure/include, and similar.
I know this must be evident to coders, but I think it's a serious obstacle to the rest of us.