paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update storybook url

Browse Source
This commit is contained in:
Patrik Oldsberg
2020-08-14 09:20:09 +02:00
parent a82f780726
commit 7c4307d1ee
8 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+1 -1
View File
@@ -41,7 +41,7 @@ The current documentation is very limited. Help us make the `/docs` folder come
## Contribute to Storybook
We think the best way to ensure different plugins provide a consistent experience is through a solid set of reusable UI/UX components. Backstage uses [Storybook](http://storybook.backstage.io).
We think the best way to ensure different plugins provide a consistent experience is through a solid set of reusable UI/UX components. Backstage uses [Storybook](http://backstage.io/storybook).
Either help us [create new components](https://github.com/spotify/backstage/labels/help%20wanted) or improve stories for the existing ones (look for files with `*.stories.tsx`).
README.md
+2 -2
View File
@@ -29,7 +29,7 @@ For more information go to [backstage.io](https://backstage.io) or join our [Dis
We created Backstage about 4 years ago. While our internal version of Backstage has had the benefit of time to mature and evolve, the first iteration of our open source version is still nascent. We are envisioning three phases of the project and we have already begun work on various aspects of these phases:
- 🐣 **Phase 1:** Extensible frontend platform (Done ✅) - You will be able to easily create a single consistent UI layer for your internal infrastructure and tools. A set of reusable [UX patterns and components](http://storybook.backstage.io) help ensure a consistent experience between tools.
- 🐣 **Phase 1:** Extensible frontend platform (Done ✅) - You will be able to easily create a single consistent UI layer for your internal infrastructure and tools. A set of reusable [UX patterns and components](http://backstage.io/storybook) help ensure a consistent experience between tools.
- 🐢 **Phase 2:** Service Catalog ([alpha released](https://backstage.io/blog/2020/06/22/backstage-service-catalog-alpha)) - With a single catalog, Backstage makes it easy for a team to manage ten services — and makes it possible for your company to manage thousands of them. Developers can get a uniform overview of all their software and related resources, regardless of how and where they are running, as well as an easy way to onboard and manage those resources.
@@ -85,7 +85,7 @@ Take a look at the [Getting Started](docs/getting-started/index.md) guide to lea
- [Service Catalog](docs/features/software-catalog/index.md)
- [Architecture](docs/overview/architecture-terminology.md) ([Decisions](docs/architecture-decisions/index.md))
- [Designing for Backstage](docs/dls/design.md)
- [Storybook - UI components](http://storybook.backstage.io)
- [Storybook - UI components](http://backstage.io/storybook)
## Community
docs/README.md
+1 -1
View File
@@ -74,7 +74,7 @@ better yet, a pull request.
- [Glossary](auth/glossary.md)
- Designing for Backstage
- [Backstage Design Language System (DLS)](dls/design.md)
- [Storybook -- reusable UI components](http://storybook.backstage.io)
- [Storybook -- reusable UI components](http://backstage.io/storybook)
- [Contributing to Storybook](dls/contributing-to-storybook.md)
- [Figma resources](dls/figma.md)
- API references
docs/dls/contributing-to-storybook.md
+1 -1
View File
@@ -4,7 +4,7 @@ title: Contributing to Storybook
---
You find our storybook at
[http://storybook.backstage.io](http://storybook.backstage.io)
[http://backstage.io/storybook](http://backstage.io/storybook)
## Creating a new Story
docs/dls/design.md
+1 -1
View File
@@ -111,7 +111,7 @@ picked up by our team as something to be added to our design system.
## ✏️ Resources
**[Storybook](http://storybook.backstage.io/)** - where you can view our
**[Storybook](http://backstage.io/storybook)** - where you can view our
components. If you’d like to help build up our design system, you can also add
components we’ve designed to the Storybook as well.
docs/overview/roadmap.md
+1 -1
View File
@@ -11,7 +11,7 @@ project and we have already begun work on various aspects of these phases:
- 🐣 **Phase 1:** Extensible frontend platform (Done ✅) - You will be able to
easily create a single consistent UI layer for your internal infrastructure
and tools. A set of reusable
[UX patterns and components](http://storybook.backstage.io) help ensure a
[UX patterns and components](http://backstage.io/storybook) help ensure a
consistent experience between tools.
- 🐢 **Phase 2:** Service Catalog
mkdocs.yml
+1 -1
View File
@@ -74,7 +74,7 @@ nav:
- Glossary: 'auth/glossary.md'
- Designing for Backstage:
- Backstage Design Language System (DLS): 'dls/design.md'
- Storybook -- reusable UI components: 'http://storybook.backstage.io'
- Storybook -- reusable UI components: 'http://backstage.io/storybook'
- Contributing to Storybook: 'dls/contributing-to-storybook.md'
- Figma resources: 'dls/figma.md'
- API references:
packages/storybook/README.md
+1 -1
View File
@@ -1,6 +1,6 @@
# storybook
This package provides a storybook build for Backstage. See [storybook.backstage.io](http://storybook.backstage.io)
This package provides a storybook build for Backstage. See [http://backstage.io/storybook](http://http://backstage.io/storybook)
## Why is this not part of `@backstage/core`?