Closed benjdlambert closed 9 months ago
Initial support for Internationalization (i18n) has been added to Backstage in the upcoming 1.18.0
release and with Hacktoberfest coming up it would be a good opportunity to let the Community know about this and ask for help with translations 🚀
Docs: https://backstage.io/docs/plugins/internationalization/ Initial PR: https://github.com/backstage/backstage/pull/17436 Usage example PR: https://github.com/backstage/backstage/pull/19786
Meta Issue for tracking: https://github.com/backstage/backstage/issues/20191
Question I hope could be answered in todays session, what is the plan for UI components going forward?
With components I am thinking about: https://backstage.io/docs/dls/component-design-guidelines
Especially adding new component types or variations of existing components?
I see that a large amount of community plugins available in todays plugin catalog that wants their UI to look fresh or updated use MUI directly rather than the built-in components.
For plugin developers, is there any caveats into just using MUI directly rather than built-in components?
I know that some work is beeing done about the 429's on the discovery process, could you give some information about this? If i'm not wrong the work was beeing done for bitbucket, is it reusable for azure devops?
Thank you!
Details
Backstage Community
Use this to convert to your timezone
Use this to convert to your timezone
How to join the Community Session
Join the Zoom Meeting
Note: Please sign up on Zoom if you do not have an account. This meeting requires a Zoom account for joining.
In case you face issues joining - feel free to use the
#meetup
channel on Discord.Action Required