User Interface (UI) / User Experience (UX) · Articles & templates · Created by
Rilameth
completed
vehicle-template vehicle template beam width
What functionality is missing? What is unsatisfying with the current situation?
For most people, the term "beam" is baffling as a field (for ships it means "width", but not everyone creating vehicles knows about ship terminology). It becomes more baffling with no "width" field. This confusion can throw off more interruption-sensitive workflows, and also result in the wrong values being put into the field (due to misunderstanding what it means).
How does this feature request address the current situation?
Include a brief description of what is meant by "beam" (is it width? is it strength of headlights?), and if beam is something other than width, then the addition of a width field would be good too. An alternative would be to rename "Beam" to "Width", thereby making it more intuitive to more people, and for more types of vehicles than just ships.
What are other uses for this feature request?
Pretty sure it only bears relevance to the vehicle article itself. But it would remedy a workflow speedbump, and should be a fairly quick and simple change.
Follow up
Addendum: Google should not need to be used, and does not clarify which version of "beam" the template is using. Google only informs on what it could possibly be, not what is actually intended. Google is not the be-all, end-all solution, and I'm getting tired of being told to Google things that Google is unable to provide clarification on. I'm likely not the only one tired of being told to Google.
The Team's Response
Thanks for the suggestion! We've renamed Beam to Width. We're also in the process of adding description to all fields!
Current score
28/300 Votes · +3708 points