Good API documentation
Can we get somehow good and full description of Elgg API? Yes, I know about reference. site and about some articles in wiki - too. But Docuwiki output isn't well-written doc, chaotic mentions in wiki isn't solution too.
I think it can decrease gap between Elgg and some potential (but lazy and heave-loaded IRL) devs
Feedback and Planning
Discussions about the past, present, and future of Elgg and this community site.
- Kevin Jardine@kevin
Kevin Jardine - 0 likes
- Alexander Leschinsky@lazybadger
Alexander Leschinsky - 0 likes
You must log in to post replies.Why not read the source? In my experience it is well documented and the most complete and reliable information available.
Any quality inline comments don't allow to see "full elephant" at once. We just can't get this way organized, categorized in logical sections all API. Good written API, I think, will eliminate mostly such questions as here, here, here, here... Some more deep concepts as metadata (and using it), subtypes, views in common and Elgg-specific output functions... can be explained more fully
Just thinking, not complaints at all