Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A How to include external references when writing internal documentation?

I like Monica's answer -- my answer here is about how to be sure these links are still viable in the future. If others are also making the documents, I encourage "casual citation", so there's no...

posted 5y ago by April Salutes Monica C.‭  ·  last activity 4y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2020-02-10T14:22:55Z (about 4 years ago)
Source: https://writers.stackexchange.com/a/43596
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T11:21:47Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/43596
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T11:21:47Z (over 4 years ago)
I like Monica's answer -- my answer here is about how to be sure these links are still viable in the future.

If others are also making the documents, I encourage "casual citation", so there's not the stress of Proper Bibliographic Formatting, but as long as the URL is there, then readers can get to where the writer went.

To be sure that it's still there in the future, I often advised them also to go to the WayBack Machine on Archive.org, and there's an option there to manually copy archive that specific page.

For my classes, I'd often do the archive.org thing, _then_ feed that longer link into TinyURL, so I'd have a shorter (though less identifiable) link to put on our resources, and it would show the version of the site/exercise that I planned for.

(This won't work at my workplace -- archive.org is blocked! but in most of the world, it should be fine. And it's not proof against robots.txt exclusions, which means the page won't be on archive.org.)

I do typically like to have a Visible Link, with the URL spelled out in case there's an error or change. If I copied an extra space into the link, someone can easily copy it. If the site did a redesign, with the original page title, it's a lot easier to search.

#1: Imported from external source by user avatar System‭ · 2019-03-15T19:00:09Z (about 5 years ago)
Original score: 4