Hi @Volker_E, thanks for your analysis and outlining similarities and differences. Though I must say I wouldn't see them as such big differences, more as different approaches and in order to get to ONE shared component library we should discuss how to get to the same approaches. Here are some points to consider how to come to one process:

As a food for thought for defining your ideal proces you may want to look into the process of Designing Components that @Sarai-WMDE has created.

Resolved by completing T257846

Is this a duplicate of T256791?

@Sarai-WMDE is this already done through the link in section 1.2 on the "how to design components" page?

Yes, if the described handover covers everything needed for developers (as indicated here), this story can be closed as well.

Maybe the idea should be added to a placeholder story so it is not lost?

Thanks a lot, @Pablo-WMDE for writing this up. I agree with your points and we should document this in some way in our storybook documentation in the "modifying components" section.

We decided to have our documentation in Storybook and will align on the general structure here: https://docs.google.com/document/d/18klqTcs11uWajeEiSSYoRaOSzE9IYE_pK6gc1CZpLKQ/edit or in a meeting. Will continously add documentation as we progress.

Following @darthmon_wmde's suggestion Github.pages could be good place to document our decisions and standards as well as a documentation how to develop system-compliant components.

Hi, I'm UX & Design lead at Wikimedia Germany and need to be able to create (sub)projects and milestones for our sprints. Thanks a lot for giving me the respective rights. Raja

Not sure if we need this story and it should be part of this hike. There are no interaction guidelines yet (unfortunately) and defining the interaction for the needed component is task of the designer in charge together with the rest of the UX team, including the DS designer.

I like this description very much, only one point: "Verification (parallel to development)": why parallel? Shouldn't it be "after development"?

@Sarai-WMDE is this still relevant or not anymore after the prototyping week?