>
> Comments are a fertile ground, and sometimes they are fertile for
> infestation of incorrect information. Unfortunately, the large bulk
> of comments in the book are this kind. It pains me to say that, as
> originally the hope was that they would be as useful as the comments
> on php.net. But sadly it just never happened. I'd also like to point
> out that there are _numerous_ documentation sets that have no
> comments, and they seem to service their communities perfectly well.
>
> By we, I hope you mean you. If you feel the current suggestion is not
> up to snuff, then please suggest a better one. Using sphinx doesn't
> occlude the possibility of using disqus for comments. jQuery does
> this for their documentation and it works.
I think that making the comments more visible would be a step in the
right direction. Better to run them at the bottom of the page than in
a weensy pop-up. By making them more prominent, perhaps errors or
misinformation would be caught earlier. Which leads to my next
suggestion: add a "flag" link to alert ... well, I'm not really sure
who should be alerted. Or, allow comments to be responded to. Although
that would mean having to display nested comments, which could become
too crowded, and, anyway, might not necessarily be the best way to
deal with incorrect info.
OK, just thinking out loud here. But please at least make the comments
more visible. There are probably some people who don't realise they're
there.
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
No comments:
Post a Comment