Mon, Jul 13
Not sure if this is still a valid task, but it's content as it is now, is covered by https://github.com/wmde/wikit/pull/73
Thu, Jul 9
Tue, Jul 7
Mon, Jul 6
Fri, Jul 3
- Chromatic adventures
Thu, Jul 2
Wed, Jul 1
Hack GitHub pages:
To achieve what we want the only option with GitHub pages is to create subpages, e.g. https://wmde.github.io/wikit/test/<branch-name>. That can happen with some specific GitHub action commands. We have to think of purging the pages themselves. We conclude that this involves us "inventing" this approach. On the other hand we are confident that other tools listed in Notes can provide all things we need, therefore we would rather try those out first and if they don't work for us for whatever reasons (including monetary ones) we will go back to github pages as a last resort.
Tue, Jun 30
Wed, Jun 24
Tue, Jun 23
Thu, Jun 18
Mon, Jun 15
Jun 11 2020
Jun 10 2020
Jun 8 2020
Maybe I'm missing something obvious, but that supposed to work in Github only and the ones here are in gerrit (can we run dependabot in gerrit? I'd be really surprised).
I see there’s already a home-brewed solution to this problem but nevertheless I'd like to leave something here:
https://dependabot.com/ - this is a bot that regularly checks for updates in a repo's dependencies. If any are found it updates them and creates a pull request. It works for various languages.
This is how it looks (on a private project of mine) - https://github.com/tzhelyazkova/schema-form-prototype/pull/3
It should be possible to be configured to work with gerrit, here's the core lib - https://github.com/dependabot/dependabot-script
Jun 3 2020
Jun 2 2020
Looks like we don't want to merge this one.
https://gerrit.wikimedia.org/r/565091 – async/await in browser tests
May 29 2020
Current size on master: dist/css/data-bridge.app.css 31.52 KiB gzipped: 4.57 KiB
Size on the related patch: dist/css/data-bridge.app.css 21.88 KiB gzipped: 3.88 KiB
May 28 2020
I assume we want Storybook as a way to communicate between UX, product and engineering. If you think it's valuable to have the Figma components alongside the Vue components, then sure let's integrate the two tools. We would have to come up with some very obvious distinction between the two sets, so people are not confused.
I cannot think of a situation where we would like to have both, though. :/
May 27 2020
May 26 2020
May 18 2020
May 17 2020
Tried it out in a fresh vue cli project here. I concluded that it's not going to be useful for the design system we want to build. Here's why:
May 15 2020
The result of the proposal:
We are going with a VueJS implementation of the Design System, where the CSS will be agnostic, as in it's going to be provided in schema driven way using design token files.
We will explore ways to export agnostic components (HTML/CSS) from the existing Vue components.