Mon, Sep 21
Aug 19 2020
Aug 18 2020
Resolved by completing T257846
Is this a duplicate of T256791?
Aug 17 2020
Yes, if the described handover covers everything needed for developers (as indicated here), this story can be closed as well.
Aug 11 2020
Aug 3 2020
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.
Jul 22 2020
Jul 14 2020
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.
Jul 13 2020
Jul 7 2020
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.
Jul 6 2020
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
Jul 2 2020
Jul 1 2020
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.
Jun 29 2020
I like this description very much, only one point: "Verification (parallel to development)": why parallel? Shouldn't it be "after development"?
Jun 25 2020
Jun 9 2020
@Sarai-WMDE is this still relevant or not anymore after the prototyping week?
Jun 3 2020
Apr 20 2020
Added links to presentation slides
Apr 17 2020
I guess we don't want to add this to the slides?
added to slides