Does Slice Machine offer a checkbox field component? I've tried adding a select field slice to reproduce a similar effect, but only one choice is allowed instead of an array.
Prismic really needs a checkbox component and a radio buttons component. Selecting multiple options within a dropdown menu can be very annoying.
Hi Scott,
Thanks for the feedback. I can see how having some sort of multi-select could be useful, but can you tell me more about your exact use case?
Without knowing your use case, a workaround might be too add the select field in the repeatable zone of your Slice so you make many selections.
Either way, I've marked this as a feature request and passed it to the team.
Thanks.
I'm also interested in this post.
I'm more interested in checkboxes than radio buttons, but it lacks a variety of field types that can be used in the backend.
For example, I need a checkbox with multiple color options.
Currently, I have to create a custom type "Colors" and use a repeatable group with a content relationship. Sometimes, it would be more convenient to have something simpler, like a checkbox, similar to how the select field works.
This would also be interesting for radio buttons.
It may seem trivial, but compared to other Headless tools of the same kind, your range of field types is quite limited. It's a shame considering the quality of the rest.
Hey there!
Thanks for coming back on this topic. Now that we have opened the "modeling" topic/track in our DevTools team, this use case in under our radar.
Could you elaborate on the exact use case where you need a "checkbox" field? Why a checkbox as an individual field and not something like a multi select or so?
Ideally, could you share a screenshot of the design you want to implement so we have the exact usecase?
Thanks for your help!
Hi
I've also wanted this feature a few times and my use case is around filtering lots of features on a product list that has 20+ slices, especially long lists of features where multiple could be applied. At the moment I have a boolean field for each key feature which really bulks the slice out; Where a list of checkboxes with a label would make more sense, I could then receive that field as an array of named features or an obj key name boolean.
Thank you for your continued interest in enhancing Prismic’s field capabilities. As part of our ongoing efforts to improve content modeling, we’re exploring the introduction of new field types, including checkboxes and radio buttons.
To better understand your requirements, could you please provide more details about your specific use case? For instance:
• Why do you prefer using individual checkboxes over a multi-select dropdown?
• Could you share a screenshot or description of the design you’re aiming to implement?
Your insights will help us tailor our development to meet your needs effectively.
Additionally, we’ve recently improved the link field to include text, style variants, and repeatable options without the need for a group. This enhancement might offer a more streamlined solution for certain use cases. 
We appreciate your feedback and look forward to your response.