Skip to content
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

review current design of Extensions workflow #6757

Open
benoitf opened this issue Apr 11, 2024 · 2 comments
Open

review current design of Extensions workflow #6757

benoitf opened this issue Apr 11, 2024 · 2 comments
Labels
area/extensions 🧩 kind/enhancement ✨ Issue for requesting an improvement

Comments

@benoitf
Copy link
Collaborator

benoitf commented Apr 11, 2024

Is your enhancement related to a problem? Please describe

here are screenshots of updated implementation of the extensions page to iterate / gather ideas

It should ordered by priority like:

  • must have before being merged
  • need follow-up as it's still better than what we have so we can't hold for a while
  • potential increment

Describe the solution you'd like

Collect feedback / options

for example some people dislike the redundancy of the word 'extension', start/stop could be activate/deactivate or enable/disable
replace DD extension label by Docker Extension

bigger icons for extensions, removal of some content, adding description of the extension

in extension detail page, background color of the sidebar, scrollbar, etc

here are the screenshots:

  • Extension List:
    image

  • Extension List filtering
    image

  • Extension Details
    image

  • Extension Catalog
    image

  • Custom Install
    image

image

Describe alternatives you've considered

No response

Additional context

No response

@benoitf benoitf added the kind/enhancement ✨ Issue for requesting an improvement label Apr 11, 2024
@vzhukovs
Copy link
Contributor

One of the most potentially motivating things to the users will be an additional button near Install Custom... called Create Own or Develop an Extension, that will generate the skeleton of the empty extension or the simple one, like hello world. From what I see, we're missing such things. We have the ability to install an extension, but there is no information how to develop them on the UI. Could be useful I think.

@axel7083
Copy link
Contributor

That's a lot of work, it is already such an impressive upgrade 👍 ! I have some comments, based mostly on how I feel with the implementation. (Nothing I listed is a necessity and falls under the need follow-up as it's still better than what we have so we can't hold for a while)

Navigation

image

IMO the Puzzle icon should be at the bottom as it is more a settings/configuration items rather than a resource or utility.

Extension List

The choice of the icons feel odds to me.

  • Setting Gear for onBoarding
  • Paper Edit for opening preferences

I would have something like a rocket or even a plane, to really show the action of on boarding

Rocket Plane
image image

I have some issue with the actions button, as the settings (gear) is disabled, I would not show it if the action is not available. Also to use the spaces available, I would have placed it at the top right of the card.

The different design buttons grouped all together feel very weird to me.

Extension Resource
image image

The open details icon also feel strange, as it should be on the right to keep the consistency with the resource page

Extension Details

I do not really like the extension details, as I have a feeling that the layout is not consistent with the application, having a scrolling container in the middle with some informations sticking on the right feel odds...

I am taking the JetBrain Plugin page as an example here

image

I am wondering if we should not move the version and author to the top, then they will still stick to the top, without having this weird (IMO) card on the right, which is not really bringing much information in reality.

Moreover, if we really want a dedicated places for more information, tabs could be a solution, as shown in the JetBrain example.

Custom Install

Maybe the placeholder's input should not be the place with all the details, and have some text above to give some details ?

Extension Catalog

image

The card layout feel too big, why so much unused spaces ?

image

Why do we use a header here Available extensions when we do not have one for the Installed one? I think we could remove it, as it does not bring a lot of information, since we already are in the Catalog tab, meaning that it is listing the available one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions 🧩 kind/enhancement ✨ Issue for requesting an improvement
Projects
None yet
Development

No branches or pull requests

4 participants