-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Ag-stuff wiki
Moved from https://github.com/AndyGlew/Ri5-stuff/wiki/Home---Ri5-stuff---=:--AndyGlew
See AndyGlew locations on GitHub
2023-12-21: Test
2022-04-26: Tabular Email Searches
2022-03-16: Tests and Experiments with this GitHub wiki
2022-02-08: GitHub-wiki-is-a-pain in HFIM-BS/wiki
But I use it because it is an okay watch.
Once again, can't get all the features I want in one product.
I don't really care what documentation tool or markup language I am using. LaTeX, Word, LibreOffice, various Wiki markup languages like twiki or MediaWiki, Markdown, AsciiDoc, emacs Org mode... whatever.
Well, actually I do care, but none of them have the features that I want. At least, no single one of them has all of the features that I want , and for the most part many of them don't have any the features that I consider most important. Hence this Wishlist and Bitchlist.
There are many different tools where you can discuss, record, and/or track work in progress. These include
- issue trackers
- mailing lists and probably less common
- wikis
- fora such as website forums, newsgroups, notes files
- shared file systems
- pull request documentation
Each has their own pros and cons. Many projects use more than one. In [Recording and Tracking Work In Progress: Issue Trackers, Mailing Lists, Wikis, etc]] I discuss them, and espouse my personal BKMs.
AsciiDoc is supposedly the RISC-V standard documentation forward going forward. Too bad.
GitHub Wiki bitch:
- Is it possible that the GitHub wiki links/references break when their target page name changes?
- It's one thing to have the link text not be updated, but to break the link?
- I think I just saw this happen, but I hope that I am wrong