Clean up legacy docs #19
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Jafner/Jafner.net#19
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Review the docs directory with the ultimate goal of migrating to a docs-beside-code approach.
We don't want to erase institutional knowledge, but we also want to ensure our docs are maintainable and useful.
Future issues will concern building systems to keep our docs "alive".
Many of our docs were created expressly to document imperative steps taken that cannot otherwise be represented in code, but may need to be taken again.
How do we want to store information like this? Generally, this information is "dead" in the sense that it does not actively serve any of the purposes of the repo. But it may be useful again as a shortcut to relearning the described procedure(s).
All legacy docs in the docs directory have been handled.