-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Add "Get Started" content to extension detail #118055
Comments
I assume that this extension getting start page shall be contributed by the running extension right thereby it is available only when extension is installed? |
Correct, this would only appear if an extension contributes a getting started item. |
Makes sense. In such case we need to add API for extensions to contribute welcome pages. How about updates release notes for extensions? |
@JacksonKearl would have a better answer for this, but we recently allowed extensions to contribute getting started content with #116414. Next steps is to allow extensions to contribute multiple getting started content and extensions can set a property for the one that is shown on the extensions detail page post-install. The idea is that this can be used for both getting started and release notes/calling out new features. |
My understanding is that we're no longer pursuing this route in favor of some alternative way of showing the content, such that the user doesn't need to open the getting started page or extension editor to see the content. |
Screen.Recording.2021-03-03.at.9.34.03.AM.mov
Refs #116414
This is based on the work of #106715 and how we've added support for extensions to contribute to this (#116414). One idea to bring this content more in context of where the user is at is when an extension is installed. Currently we show the readme in the "Details" tab, but I think showing the get started content for the extension on this page is more appropriate and can prevent extensions from creating their own "welcome pages".
The text was updated successfully, but these errors were encountered: