Merge pull request #4767 from adamdmharvey/storybook-tips

docs: Update design info with more Storybook details
This commit is contained in:
Adam Harvey
2021-03-03 15:27:45 -05:00
committed by GitHub
4 changed files with 39 additions and 8 deletions
Binary file not shown.

Before

Width:  |  Height:  |  Size: 47 KiB

After

Width:  |  Height:  |  Size: 246 KiB

+33 -5
View File
@@ -4,8 +4,38 @@ title: Contributing to Storybook
description: Documentation on How to Contribute to Storybook
---
You find our storybook at
[http://backstage.io/storybook](http://backstage.io/storybook)
The Backstage Storybook provides you a way to explore reusable Backstage User
Interface elements and how to use them in developing the Backstage core and its
plugins. These UI elements are commonly called "components", and include things
such as buttons, tables, specialized widgets with specific formatting, and so
on.
You'll find our storybook at
[http://backstage.io/storybook](http://backstage.io/storybook).
As noted in the [design introduction](design.md), Backstage's design is based
off of [Material-UI](https://material-ui.com/). Much of the UI elements use
direct Material-UI, while we've also extended and written custom ones to provide
specific functionality.
![Storybook Page](../assets/dls/storybook-page.png)
Storybook "Stories" are used to provide examples for how to use a specific
component, which are then displayed both visually and with sample code to be
copied.
When custom Backstage components are created, they are placed in the
`@backstage/core` package and added to the Storybook.
There may be times where an existing Material-UI component (in
`@material-ui/core`) is sufficient and doesn't need to be wrapped or duplicated.
However, we may want to identify an _opinionated_ way to use that component
inside of Backstage. In these cases, stories showing how to use those existing
components will also be put into our storybook.
When a story example using Material-UI becomes more complex, requiring a
specific set of colors, variants, parameters, etc., it may become a candidate to
be refactored to become a full Backstage core component.
## Creating a new Story
@@ -33,12 +63,10 @@ core
Go to `packages/storybook`, run `yarn install` and install the dependencies,
then run the following on your command line: `yarn start`
![](../assets/dls/running-storybook.png)
![Storybook command startup](../assets/dls/running-storybook.png)
_You should see a log like the image above._
If everything worked out, your server will be running on **port 6006**, go to
your browser and navigate to `http://localhost:6006/`. You should be able to
navigate and see the Storybook page.
![](../assets/dls/storybook-page.png)
+4
View File
@@ -127,6 +127,10 @@ your own plugin for Backstage.
**[Discord](https://discord.gg/EBHEGzX)** - all design questions should be
directed to the _#design_ channel.
**[Customize Backstage's look and feel](https://backstage.io/docs/getting-started/app-custom-theme)** -
How to customize the look and feel of your Backstage instance by extending the
theme.
## 🔮 Future
### Contributions from designers
+2 -3
View File
@@ -1,9 +1,8 @@
---
id: template-legacy
title: Writing Templates (Legacy)
description:
Old documentation describing the backstage.io/v1alpha1 format of the Template
Schema
# prettier-ignore
description: Old documentation describing the backstage.io/v1alpha1 format of the Template Schema
---
## Kind: Template