Timeline for answer to Warlords of Documentation: A Proposed Expansion of Stack Overflow by zwol
Current License: CC BY-SA 3.0
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2015 at 1:59 | comment | added | Mikl | @Juffy (last part of previos comment) In this situation with php docs it's simpler, if you learn php you can just go throw all of it's basic reference (it can be done very quickly), and you will have nearly all information you need at first steps. | |
| Sep 10, 2015 at 1:58 | comment | added | Mikl | @Juffy it's a good example of problem with comments management, if you need to divide one page into several and change the page type to category for this sub pages. I think in previous version there was one big page for variables. By the way, this problem can be on every platform, and on SO too, the example is there is some near the same questions that has different number of valuable answers and to read all of this you need to go throw all of this questions. | |
| Sep 10, 2015 at 1:41 | comment | added | zwol | @Juffy Why did I click that link. Why. goes in search of the brain bleach | |
| Sep 10, 2015 at 1:30 | comment | added | Juffy | @Mikl - sorry, I should have restricted that just to the comment system. As a PHP noob though, the comments are generally massively unhelpful for the page they're on. Trivial example here - this is the friggin' contents page for the Variables section, not the page on how to initialise variables in strange and interesting ways. Why is there any comments on a page with no content other than four links? There's even a specific page for variable variables, but that comment isn't there. /rant | |
| Sep 9, 2015 at 22:31 | comment | added | Mikl | @Juffy PHP documentation are very good structured (tree structure of reference and structure of each topic itself), has great many versions and languages support, has both good and bad comments and the way to up/down vote those comments. And more valuable it has platform for community to contribute and improve this documentation, i think, it worth having to look at it's good parts and take all good experience it has. | |
| Sep 8, 2015 at 6:23 | comment | added | Juffy | Oh good, I'm not the only person who thinks the PHP docco (and comment process) is a cesspit. The problem, as I see it, is that people don't comment to improve the docco - they comment to advertise their fancy workaround/solution/hack/bodge for a bug/feature that may or may not exist. I would rather read experts-exchange than a comment thread on php.net. | |
| Sep 7, 2015 at 14:38 | comment | added | zwol | @rjmunro Yes, the PHP documentation itself is fine. It's only the user-submitted commentary, and in particular, the way the PHP core organization neglects it and considers themselves not responsible for its quality, that should serve as a cautionary tale for this proposal. | |
| Sep 7, 2015 at 11:12 | comment | added | rjmunro | I've always thought that the PHP documentation is really good, probably the languages greatest strength, as long as you ignore the comments. I particularly like the way you can type php.net/[function-name] into your address bar and get to the right page in one step. | |
| Sep 1, 2015 at 16:26 | comment | added | Ajedi32 | "making sure that documentation finds its way back to upstream open-source projects" Yes, this. IMO this would mostly solve the fragmentation problem people have been expressing concern over. | |
| Aug 31, 2015 at 19:26 | history | answered | zwol | CC BY-SA 3.0 |