You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user is creating a template in Coder from a starter template, they are asked to decide on a bunch of template settings that impact day 2 behavior.
As this may be one of the first workflows in Coder, it creates a significant amount of cognitive load for a new user. I suggest we remove all of these fields (surrounded by red rectangle) on the "create template" screen and create it with the default values:
In comparison, GitHub's "create repo" screen is quite small even though GitHub repos have significantly more settings than Coder settings.
Imagine somebody had to go through all repo settings before creating:
If a user needs to change a setting after creating a repo, they go into the settings for the repo for the full view
Note on "Duplicate"
I think, in many other software platforms, "Duplicate" actions will take you directly to the duplicated resource, not a create form where the user can make modifications before creation.
However, if we want to keep the current duplicate flow, perhaps we could hide the complex fields under "Advanced"
The text was updated successfully, but these errors were encountered:
And we may hide/remove all enterprise settings if no licence/trial is available.
I am not sure about this as we also need a way to advertise enterprise features within the product.
When a user is creating a template in Coder from a starter template, they are asked to decide on a bunch of template settings that impact day 2 behavior.
As this may be one of the first workflows in Coder, it creates a significant amount of cognitive load for a new user. I suggest we remove all of these fields (surrounded by red rectangle) on the "create template" screen and create it with the default values:
In comparison, GitHub's "create repo" screen is quite small even though GitHub repos have significantly more settings than Coder settings.
Imagine somebody had to go through all repo settings before creating:
If a user needs to change a setting after creating a repo, they go into the settings for the repo for the full view
Note on "Duplicate"
I think, in many other software platforms, "Duplicate" actions will take you directly to the duplicated resource, not a create form where the user can make modifications before creation.
However, if we want to keep the current duplicate flow, perhaps we could hide the complex fields under "Advanced"
The text was updated successfully, but these errors were encountered: