tasks: Update User guides task descrtipion for GCI 2017. #630
Conversation
tasks/2017/user-guides.md
Outdated
| * If this is your first contribution, you may be interested in the | ||
| [how to create a pull request](https://codein.withgoogle.com/tasks/6541581402243072/) task. | ||
| * **Completion of the | ||
| [submit a pull request](../submit-a-pull-request.md) task**. The task helps |
There was a problem hiding this comment.
Shouldn't this be ./submit-a-pull-request.md?
tasks/2017/user-guides.md
Outdated
| your browser on `http://<hostname>:9991/help/<feature>`, where | ||
| `<hostname>` is either `localhost` or the hostname of your VM, and | ||
| `<feature>` is the name of the feature. | ||
| Well-written user documentation help users and search engines discover Zulip |
|
Looks great, merged! I think we might want to resurrect a variant of "task type B" where their job is to go through a group of 5 articles, try to follow the instructions somewhat blindly, taking notes on what didn't work. And then also compare with the UI and see what other articles should possibly be link. And the work product is a list of things about that documentation that can be improved. I think we could have ~20 tasks that way (by grouping articles; I think we want each to involves carefully reviewing ~3-5 pages of text). @synicalsyntax also, we should produce a script with a list of articles to write. I'd shy away from the "document app X" articles that didn't happen last year for early tasks, since I think the reason they didn't happen is they're larger/more difficult projects, and we want to start with 20+ user docs tasks that are easy to do. |
|
Opened #635 for the new task. |
No description provided.