summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web>2014-04-19 13:26:38 +0000
committerGravatar admin <admin@branchable.com>2014-04-19 13:26:38 +0000
commit2abe6de4adda56bd3846b533bcda1d222fb75687 (patch)
treec20485e47e714d0070ef106325ba475d89914ac8 /doc
parent65a84a86802df4fd0a6243813fd11cc1bc6809c4 (diff)
how about a more complete manual, even?
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/build_a_user_guide.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/todo/build_a_user_guide.mdwn b/doc/todo/build_a_user_guide.mdwn
new file mode 100644
index 000000000..97414391b
--- /dev/null
+++ b/doc/todo/build_a_user_guide.mdwn
@@ -0,0 +1,3 @@
+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]]