Review the intro to a feature's doc; update it with _why_ it would be used
As part of the Contribute Challenge: Beautify The Docs, we are trying to improve feature adoption through documentation.
Oftentimes a user, customer, or prospect will review a doc page when considering what parts of GitLab to use, and whether they may need to subscribe or upgrade their subscription. It's important to give more context so that they can appreciate the benefits of a given feature: why use it -- not just what it does. (This might include who it's for and what circumstances it might address, and specific expected impact, e.g. greater efficiencies in some area of development.)
To contribute:
- Find a page for a feature on docs.gitlab.com. (It can be a subsection of a page, covering a specific feature.) You can start by finding the feature on https://about.gitlab.com/features and using the doc link.
- Click "Edit this page" at the bottom (or the Web IDE link) and make your changes.
- Raise an MR and label it with Contribute2020-challenge & ~"workflow::In review". Please associate your MR with this issue.
- Repeat! (You can do this for multiple features.)
Ask any questions in #Contribute2020-challenge or see the epic.
Edited by Mike Lewis