Post History
The guiding principle in my experience is: put the link where the reader needs the referenced information. Examples: "This interface is like Somebody Else's Thing (link, or make SET a link itsel...
Answer
#3: Attribution notice added
by
System
·
2019-12-08T11:21:46Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/43592 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
The guiding principle in my experience is: put the link where the reader needs the referenced information. Examples: - "This interface is like Somebody Else's Thing (link, or make SET a link itself), and in addition..." -- put the link right there, because somebody unfamiliar with SET will need to at least skim the linked text to understand what you're about to say. - "Stuff, stuff, and more stuff... Related background information: (links)" -- here your linked information is optional background stuff; a reader could skip it entirely and not be worse off. The "links" section you've described works fine for that. Most cases will be somewhere in between -- the linked information is _helpful_ but not _required_. For these cases, you need to make a judgement call. If there are few links and you can add them "inline" (like in the first example) without making your document cumbersome, put them there because that's easier to both read and maintain. If there are lots of links and they're mostly tangential, collect them at the end -- and try to review the list from time to time to see if they're all still relevant.
#1: Imported from external source
by
System
·
2019-03-15T18:42:55Z (over 5 years ago)
Original score: 4