diff options
| author |  https://anarc.at/openid/ <anarcat@web> | 2017-01-17 16:59:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-01-17 16:59:15 +0000 |
| commit | 27ceab6929204f6cdda66c0e862897e73f2d4ca3 (patch) | |
| tree | 29919074545c8e500d05b4d80ff9084b7c4a7cdc /doc | |
| parent | c161418f7b3607a0ba686b03a3fc5f6bb0c32de7 (diff) | |
link to the workflow page
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/build_a_user_guide.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/build_a_user_guide.mdwn b/doc/todo/build_a_user_guide.mdwn index 97414391b..44b350eb4 100644 --- a/doc/todo/build_a_user_guide.mdwn +++ b/doc/todo/build_a_user_guide.mdwn @@ -1,3 +1,5 @@ there's a lot of good documentation on this wiki, but it's hard to find sometimes. it's also unclear if we should look in the [[git-annex]] manpage or elsewhere in the wiki or where. this is a typical problem with the use of wikis for documentation: it's there, but hard to find. it doesn't mean a wiki shouldn't be used but, as with any user manual, special care needs to be taken about structure, organisation and making sure the manual is exhaustive. a good example of this problem is [[todo/document_standard_groups_more_extensively_in_the_UI]]. --[[anarcat]] + +update: a beginning of this may be the the [[workflow]] page but it lacks a lot of details... |