Issue Regarding - /components/selector-strip

I want to...

[ ] Propose an update to an existing design.
[ ] Report a bug with the current documentation.
[ ] Work with the team to build a new pattern for to be considered for inclusion in Helix.
[x ] Other, explain below I'm using the Helix Selector strip in my design for image selection. See here: https://e39dx6.axshare.com/#g=1&p=1_1

In theory I am using it per recommendations/guidelines but it seems a little visually cumbersome owing to the length of the words in the selector options.

So, based on my need, can we augment the Hlix system to address my need or provide alternate advice int he docs by way of a recommended best practice for this sort of need?

How would you like to collaborate with us on this issue?

[ ] I’d like to communicate via GitHub
[ x] I’d like to communicate via Slack
[ ] I’d like the Helix team to handle it from here

Tell us more about your request.

What do you need?

a design pattern or recommendation

What problem will this solve?

customer should know at a glance how to make an image selection, without a yes no selector or primitive HTML radio button

Which Rackspace UIs, business stakeholders, or customers might benefit from this?

All Hypervisor customers and potentially Bare Metal customers

What release deadlines depend on this work?

Possibly March time frame for HyperV and April 9th 2019 for Bare Metal

How does this enhance the Rackspace experience?

Simplicity, less questioning, intuitive visual approach

rackerlabs / design-system