[documentation] [Documentation bug] link in footnote as background information?

[beginner]

Issue status update for 
http://drupal.org/node/57941
Post a follow up: 
http://drupal.org/project/comments/add/57941

 Project:      Documentation
 Version:      <none>
 Component:    Developer Guide
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  beginner
 Updated by:   beginner
 Status:       active

Well, feel free to close this issue if you feel it's not warranted.


I was thinking it could be worthwhile to add that issue as a link in a
footnote, because it provides more background information, and that
documentation page was at first a comment on that issue.


(the original title was:
"Extreme long comment on http://drupal.org/node/42388"
(hence the original title of this issue, wich was meant
tongue-in-cheek, in good fun, not as an insult, by the way :) )




beginner



Previous comments:
------------------------------------------------------------------------

Sun, 09 Apr 2006 07:18:27 +0000 : beginner

Maybe the title of the book page can be more descriptive:
http://drupal.org/node/53714
and the page http://drupal.org/node/42388 be referenced as a link
within the article.


and who is "I"?  We don't see the author of bookpages, so we've no idea
who says "I" within the Documentation.




------------------------------------------------------------------------

Sun, 09 Apr 2006 07:27:12 +0000 : sepeck

modified title.




------------------------------------------------------------------------

Sun, 09 Apr 2006 07:45:46 +0000 : beginner

Why leave out the reference to http://drupal.org/node/42388 ?




------------------------------------------------------------------------

Sun, 09 Apr 2006 14:34:21 +0000 : cel4145

Why include it? I look at it for a minute, and I have no idea why a bug
report that has been resolved is an appropriate link for including in
the documentation for that page. That would be the similar experience
for most people. If there is some relevant bit of information in that
project issue, the more effective way would be to suggest a change to
the documentation that includes the necessary explanation.