It would be great to have reusable fields. For instance, if I create a select field on one slice, I could then use it across multiple slices without needing to recreate it each time. :)
Thanks for the suggestion. I think I understand the idea, but can you clarify a bit more on exactly what you're imagining here?
Thanks.
Thanks @alexander.nilsson_pr ! Indeed this is something we here a lot from our users, and we are thinking about potential solutions. However I can't say this is an immediate priority for the team.
Best,
CĂ´me
That said, @alexander.nilsson_pr, for your last example, you are actually creating buttons/ctas using a group. For this use case we are actually improving the link field so you can add a text (already shipped since Slice Machine version 2.8.0), add style variants and make it repeatable without the need of a group (upcoming releases).
Which, for this use case, means that you would just have to use a single link field.
That sounds great! So, if I create a custom type called ButtonGroup, can I use it as a content relationship and fill in text and colors within the slice I'm currently working on?
Did I get that right? 
@alexander.nilsson_pr it's not exactly like that. What I mean is this, here is the design of what we are building.
You can just add a link field, and it will contain all the features you need. However, about the reusability of the configuration of the field, that is not possible indeed.
Coming here late and following up, another way that could be easier to implement that would solve for this (and my own) use case would be to make slice types able to be duplicated based off template in the same way that variants are. Having a template slice type to start from and duplicating it would be really helpful to my workflow, since I have to spend a decent amount of time rewriting and copying fields that every type I make will have.
In theory I could just have one slice type and use the variant feature to do this, but I think the output of one slice ends up being confusing to my content editors, and I end up with Way too many variants.
Would love to know if this would be possible!
cheers
Tucker
Hi @Tucker_Lemos ,
Thanks for the follow-up! Just to clarify, are you suggesting pre-defined fields that could be reused across multiple Custom Types (like shared “Author,” “SEO,” or “CTA” fields), or more like templated field configurations (so you can quickly add a ready-made set of fields when creating a type)?
That’ll help us capture your use case correctly before passing it on to the product team.