Skip to content

remove complex settings on "create template" screen #11783

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

Closed
bpmct opened this issue Jan 23, 2024 · 4 comments · Fixed by #11918
Closed

remove complex settings on "create template" screen #11783

bpmct opened this issue Jan 23, 2024 · 4 comments · Fixed by #11918
Assignees
Labels
site Area: frontend dashboard

Comments

@bpmct
Copy link
Member

bpmct commented Jan 23, 2024

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:

Screenshot 2024-01-23 at 4 42 32 PM

In comparison, GitHub's "create repo" screen is quite small even though GitHub repos have significantly more settings than Coder settings.

Screenshot 2024-01-23 at 4 23 06 PM

Imagine somebody had to go through all repo settings before creating:

Screenshot 2024-01-23 at 4 24 02 PM

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"

@cdr-bot cdr-bot bot added the feature label Jan 23, 2024
@bpmct bpmct added the site Area: frontend dashboard label Jan 23, 2024
@stirby
Copy link
Collaborator

stirby commented Jan 23, 2024

Agree on simplification.

We're also not sacrificing visibility on scheduling defaults with the recent related workspace page updates:

@matifali
Copy link
Member

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.

@BrunoQuaresma BrunoQuaresma self-assigned this Jan 29, 2024
@BrunoQuaresma
Copy link
Collaborator

Thinking of a few solutions for this I have 2 options in mind:

  • Remove the advanced settings entirely from the create/duplicate flow since they can be edited after creation
  • Hide the advanced settings in a "Show/Hide advanced settings" collapsable panel

Any preferences?

@bpmct
Copy link
Member Author

bpmct commented Jan 29, 2024

My preference is this one:

Remove the advanced settings entirely from the create/duplicate flow since they can be edited after creation

I rarely see creation flows that include all options right away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants