Add some more docs for GitHub.

Author: theindigamer

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,29 @@
+[This is a template. Please delete irrelevant sections, including this line,
+before posting.]
+
+## Feature request
+
+* Short description (2-3 lines)
+
+* Long description (optional)
+
+* Suggested test cases, if any
+
+## Bug report
+
+- `ozil` version (git commit):
+
+(Fill in a checkbox with an X instead of a blank.)
+
+- Issue type
+  + [ ] Unexpected crash
+    - Error message: [description here]
+  + [ ] Improper rendering
+    - [ ] Present with wide terminals (e.g. full screen-width)
+    - [ ] Present with narrow terminals (e.g. half screen-width)
+    - [ ] Present with very narrow terminals (e.g. quarter screen-width)
+  + [ ] Something else: [description here]
+
+- Test cases for reproduction (1 or more):
+
+- Screenshots (0 or more):

Contributing.md

@@ -1,6 +1,30 @@
 # Contributing
 
+## Patches
+
+* No contribution is too small. Even if it is a typo fix, please submit it!
+
+* Before you start working on something, please open an issue on the issue
+  tracker for it, or leave a comment on an existing issue.
+
+  Similarly, if you need help (while trying to write a patch), or have become
+  busy with other commitments (and hence will not be able to contribute) while
+  working on an issue, please leave a comment. Both of these are perfectly
+  understandable situations, and I will try to help if I'm able to do so.
+
+* Try to follow the conventions (e.g. naming, formatting, how imports are
+  organized) of the surrounding code.
+
+* Force-pushing to pull request branches is perfectly okay. Not having a clean
+  git history is perfectly okay too. Don't sweat it.
+
 # Development notes
 
 * Use the incantation `rg "\\\\[^ -]+" man.1 -N -o | sort | uniq` to obtain
   the list of escape codes under use in `man.1`.
+* To see list of directives at line-start across all man files -
+  ```
+  cd /usr/share/man
+  for f in ./*/*.gz; do gunzip --stdout "$f"; done \
+     | rg "^\\.[[:alpha:]]{1,2}" -o -U | sort | uniq -c
+  ```

Readme.md

@@ -3,7 +3,8 @@
 `ozil` assists you with viewing man/help pages. It is intended as a
 porcelain for `man`/`--help` + `less`/`more`/`most`.
 
-[Note: Support for man pages is not yet ready.]
+[Note: Support for man pages is not yet ready. If you try to read a man page,
+`ozil` might crash or display something weird.]
 
 ## Table of contents
 
@@ -45,9 +46,11 @@ porcelain for `man`/`--help` + `less`/`more`/`most`.
 
 ### Planned
 
--   Basic options to customize appearance (with hot-reloading).
--   Proper man page support (fill remain check-boxes in Feature list).
--   Search text (see [issue 10](https://github.com/theindigamer/ozil/issues/10)).
+- Proper man page support (fill remain check-boxes in Feature list). Given the
+  variety of macros present in man pages, this is a big task, so please have
+  some patience. :sweat_smile:
+- Basic options to customize appearance (with hot-reloading).
+- Search text (see [issue 10](https://github.com/theindigamer/ozil/issues/10)).
 
 ## Platforms
 
@@ -83,7 +86,8 @@ see the help for `foo bar` (where `bar` is a subcommand of `foo`) run
 `ozil 'foo bar'`.
 
 If you're want a man page from a specific section (e.g. `man(1)`), you
-can use `ozil man.1`.
+can use `ozil man.1` (Note: This might still crash as documented at the
+beginning of the Readme).
 
 That's mostly it. `ozil` will guide you as needed. In case of
 ambiguities, it will present you with an option to make a choice and