Chatted with @kylecarbs a bit, it looks like this was done in order to have consistent validation and pretty URLs across objects. Perhaps a template could have a label aws-linux and slug Develop on Linux with EC2

Spaces I understand for URLs but underscores?

Also, we've trimmed down the number of places where we use a name in the URL; is that true of templates as well? Given anticipated future template namespacing, seems like the template name has pros and cons for use in the URL.

@ketang Yeah I couldn't identify a use for underscores, so not sure why I included it. I'll change the issue title.

Also, we've trimmed down the number of places where we use a name in the URL; is that true of templates as well? Given anticipated future template namespacing, seems like the template name has pros and cons for use in the URL.

Yep, still in the URL

@bpmct I updated the title to say that a display name should exist instead. I still think the slug naming is helpful.

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

Looking at this one.

Hey @bpmct! Could you please confirm the scope of this issue:

1. Introduce an extra property for templates: display_name. Display names can have spaces.
2. Add CLI flag to coder templates create <template-name> --display-name <display-name>
3. Use the "display name" on the template page like https://dev.coder.com/templates/aws-linux. When "display name" is undefined, just use "name".
4. Slug (for instance, .../aws-linux) is left as is.

Did I miss anything? Should it be possible to change the display name using UI?

Hey @mtojek. Love this. Will it also use the template display name on other pages, such as the workspace page and workspaces list?

Did I miss anything? Should it be possible to change the display name using UI?

For consistency's sake, I think the display name should be managed just like the icon and description properties (via coder templates edit and the UI).

Will it also use the template display name on other pages, such as the workspace page and workspaces list?

That's the plan and I hope it's doable.

For consistency's sake, I think the display name should be managed just like the icon and description properties (via coder templates edit and the UI).

Ok, so it seems that instead of coder templates create <template-name> --display-name <display-name> we can go with templates edit. Please correct me if I'm wrong.

Yep! That makes sense :)