@Sarai-WMDE @bmartinezcalvo I added some quickly sketched out versions of things we discussed, just to get the ball rolling

In T325553#8478460, @alexhollender_WMF wrote:

@Sarai-WMDE @bmartinezcalvo I added some quickly sketched out versions of things we discussed, just to get the ball rolling

Thank you for sharing @alexhollender_WMF. At first glance I think the hide/pin buttons are better when they are closed to the "Content" title. In the proposal where the hide/pin is on the right it seems to be in the middle of nowhere and it could be related more with the article toolbar than with the Content title. Maybe if the ToC were inside a content box it would be more obvious but now they seem too separated.

Let's review the other proposals with icon only buttons to compare. It would be great to compare these proposals in one of your amazing prototypes.

@bmartinezcalvo sounds good. would it be okay for this task to be assigned to you or @Sarai-WMDE?

It would be great to see the affordance with longer terms, like “verstecken” und “anpinnen” in long-word languages like German as well for next explorations.

In T325553#8484732, @alexhollender_WMF wrote:

@bmartinezcalvo sounds good. would it be okay for this task to be assigned to you or @Sarai-WMDE?

@alexhollender_WMF I think the appropriate process for this task would be for you to work on the design explorations and then for us to find a systematic solution for that decision (e.g. if we finally go with a hide small button, we should work this new small button solution). I think it would be good to create a prototype with all the options described in the task (text button, icon button, etc.) and then decide which one is better for a user's perspective. Once the decision is taken we can create/update the system component if needed.

I have one more question, does it bother you that this text ([hide]) repeats the text in navboxes and other collapsed blocks, but works in a completely different way? It stumped me, for example. Maybe change it to [collapse] or [unpin] or smth else?

Related conversation about new smaller button variants esp when used inline in this task T327426#8549928.

important to consider the length of the text labels in various languages:

German
Russian
French
Japanese
Czech

In the latest Vector 2022 Zebra design, these buttons are implemented using a custom style. Is that tracked in a different task somewhere?

@bmartinezcalvo I wonder if this should be considered as part of T338021: [EPIC] Buttons and Inputs: Determine the approach for a large size as well.

In T325553#8988751, @CCiufo-WMF wrote:

In the latest Vector 2022 Zebra design, these buttons are implemented using a custom style. Is that tracked in a different task somewhere?

@bmartinezcalvo I wonder if this should be considered as part of T338021: [EPIC] Buttons and Inputs: Determine the approach for a large size as well.

FWIW it is referenced as part of T329963: Provide guidelines on when to choose which basic interaction element in Codex and T327426: Document how to use group of buttons for DST as it touches upon the use case for when smaller and differently styled buttons should be considered when inline, esp. when inline button groups.

In T325553#8988751, @CCiufo-WMF wrote:

In the latest Vector 2022 Zebra design, these buttons are implemented using a custom style. Is that tracked in a different task somewhere?

@bmartinezcalvo I wonder if this should be considered as part of T338021: [EPIC] Buttons and Inputs: Determine the approach for a large size as well.

@CCiufo-WMF included this as possible use case in the Figma inventory for that task.

Consider the "Using links and buttons" guidance when completing this task.

I think this task was resolved? :)