fixup
This commit is contained in:
@@ -36,16 +36,12 @@ Spotify’s developer experience offering with 2,400+ documentation sites and
|
||||
|
||||
#### TechDocs V.0
|
||||
|
||||
**Running locally**
|
||||
|
||||
- As a user I can navigate to a manually curated docs explore page.
|
||||
- As a user I can navigte to and read mock documentation that is manually
|
||||
uploaded by the TechDocs core team.
|
||||
|
||||
#### TechDocs V.1
|
||||
|
||||
**Running locally**
|
||||
|
||||
- As a user I can run TechDocs locally and read documentation.
|
||||
- As a user I can create a docs folder in my entity project and add a reference
|
||||
in the entity configuration file (of the owning entity) to my documentation.
|
||||
@@ -54,9 +50,6 @@ Spotify’s developer experience offering with 2,400+ documentation sites and
|
||||
- Documentation will be displayed under the docs tab in the service catalog.
|
||||
- As a user I can create a docs only repository that will be standalone from any
|
||||
other service.
|
||||
|
||||
**Running at company in production**
|
||||
|
||||
- As a user I can choose my own storage solution for the documentation (as
|
||||
example GCS/AWS/Azure etc)
|
||||
- As a user I can define my own API to interface my own documentation solution.
|
||||
|
||||
Reference in New Issue
Block a user