datahub/docs/README.md
Maggie Hays 4956f5a165
docs(feature-guide) Impact Analysis (#5765)
* update sidebar titles to remove About DataHub

* move impact analysis guide to new folder; update links

* update copy in Understand Data in Context section

* adding feature guide template to sidebar

* adding feature guide template

* update docs readme to link to feature guide template

* enhance docs-website readme

* add comments to feature guide template

* add links to graphql and lineage resources

* linter cleanup

* updating reference links

* update to graphql reference links

* add image and gif best practices

* update feature guide template with image details

* fix link

* update template from YouTube -> Videos

* Update docs-website/README.md

Co-authored-by: Harshal Sheth <hsheth2@gmail.com>

* update feature to Lineage Impact Analysis

Co-authored-by: Harshal Sheth <hsheth2@gmail.com>
2022-09-01 18:11:14 -05:00

51 lines
2.0 KiB
Markdown

# DataHub Docs Overview
DataHub's project documentation is hosted at [datahubproject.io](https://datahubproject.io/docs)
## Types of Documentation
### Feature Guide
A Feature Guide should follow the [Feature Guide Template](/_feature-guide-template.md), and should provide the following value:
* At a high level, what is the concept/feature within DataHub?
* Why is the feature useful?
* What are the common use cases of the feature?
* What are the simple steps one needs to take to use the feature?
When creating a Feature Guide, please remember to:
* Provide plain-language descriptions for both technical and non-technical readers
* Avoid using industry jargon, abbreviations, or acryonyms
* Provide descriptive screenshots, links out to relevant YouTube videos, and any other relevant resources
* Provide links out to Tutorials for advanced use cases
*Not all Feature Guides will require a Tutorial.*
### Tutorial
A Tutorial is meant to provide very specific steps to accomplish complex workflows and advanced use cases that are out of scope of a Feature Guide.
Tutorials should be written to accomodate the targeted persona, i.e. Developer, Admin, End-User, etc.
*Not all Tutorials require an associated Feature Guide.*
## Docs Best Practices
### Embedding GIFs and or Screenshots
* Store GIFs and screenshots in [datahub-project/static-assets](https://github.com/datahub-project/static-assets); this minimizes unnecessarily large image/file sizes in the main repo
* Center-align screenshots and size down to 70% - this improves readability/skimability within the site
Example snippet:
```
<p align="center">
<img width="70%" src="https://raw.githubusercontent.com/datahub-project/static-assets/main/imgs/impact-analysis-export-full-list.png"/>
</p>
```
* Use the "raw" GitHub image link (right click image from GitHub > Open in New Tab > copy URL):
* Good: https://raw.githubusercontent.com/datahub-project/static-assets/main/imgs/dbt-test-logic-view.png
* Bad: https://github.com/datahub-project/static-assets/blob/main/imgs/dbt-test-logic-view.png