-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backstage #731
Comments
Will be exploring this in September, any suggestions are welcome. I'm new to backstage, so any thoughts would be welcome if anyone has any. |
Ciao, a couple of notes that I hope can speedup your on boarding on Backstage. Backstage's catalog is a collection of entities. An I think that you can map a Components can provide or consume APIs Also Specs can be put inline as in the example of you can reference a file. Both in the same repo
or external as URL.
To group Hope it helps to put your head on Backstage |
Backstage and eventcatlog have more likely the same structure, so due to both tools are code driven (one with yaml and the other one with markdown) sounds like it will generate a lof of "duplication". Maybe if eventcatalog provides an iframe or something that can be embbed within a backstage entity could be a good experience. Backstage lacks of visualization about events and eventcatalog provides an amazing experience for event documentation but it lacks the rest of the backstage's features. I was doing some PoC extending backstage model creating a new |
Folks this is now live! https://www.eventcatalog.dev/docs/development/plugins/backstage/intro |
Feature Request
Backstage is a popular developer portal. It support catalogs and markdown documention. Ideally Event Catalog is integrated with it.
Some suggested options
The text was updated successfully, but these errors were encountered: