VS Code input for entering a secret is difficult to find (was: Better initial setup flow (getting API key))

[nealrichardson]

From @tareefk:

The flow to configure the Publisher should ideally ask for the URL of the server and either seamlessly acquire the API token through a login flow, or take me to the correct page on THAT instance for me to create my own key and to copy that information back into my flow. Codeium has a better flow that we could look at. I am not sure if what I am asking for is somehow insecure, but having to go to the documentation first, then go to the product UI, then copy and paste feels like a slow way to go.

Also:

Clicking on Enter a Secret brought up a UI that was very high up that I didn't see it.

[m--]

Notes from grooming:

Two issues here. First:

Clicking on Enter a Secret brought up a UI that was very high up that I didn't see it.

This is a VS Code-ism, but we could readdress from a UX perspective. We should consider if there are any other patterns we can use to surface this information to make it more readily visible/accessible from the initial interaction.

Second:

The flow to configure the Publisher should ideally ask for the URL of the server and either seamlessly acquire the API token through a login flow, or take me to the correct page on THAT instance for me to create my own key and to copy that information back into my flow. Codeium has a better flow that we could look at. I am not sure if what I am asking for is somehow insecure, but having to go to the documentation first, then go to the product UI, then copy and paste feels like a slow way to go.

Small changes here would be to give the user a better pointer to where to find this information; anything bigger will need Connect changes. That's not to say that we shouldn't do those changes; those issues should be/are tracked on the Connect side until there is Publisher work to do.

[dotNomad]

Small note that may be relevant when this is picked up - VS Code added the ability to move the Command Palette and Quick Inputs anywhere the user wants to put them:

• Drag and drop the Command Palette or any other Quick Input with snapping to center and top
• Persisted position across reloads, allowing you to set a new permanent position for Quick Inputs
• Preset positions are available in the Customize Layout picker

[nealrichardson]

Other note (which I think we discussed IRL but writing it down): Positron has more options available here for creating modals etc., so while we should have the best VS Code experience we can, we should not constrain ourselves by that.