|
|
|
# Agenda
|
|
|
|
## March 14, 2018
|
|
|
|
### Agenda
|
|
|
|
* Topics and dates for next IRL meeting
|
|
|
|
|
|
|
|
|
|
|
|
## 7 march 2018
|
|
|
|
## March 7, 2018
|
|
|
|
|
|
|
|
### Agenda
|
|
|
|
This first meeting established the new design workgroup weekly meeting, which happens so that we can keep track of what we are working on, as well as what comes next.
|
|
|
|
|
|
|
|
This first meeting installs the new design workgroup weekly so we can keep track of what we are working on and what come next.
|
|
|
|
|
|
|
|
- update on tooling: what can we share between designers, and how can we work together.
|
|
|
|
- briefing for the next phase:
|
|
|
|
To discuss:
|
|
|
|
- Update on tooling: what can we share between designers, and how can we work together.
|
|
|
|
- Briefing for the next phase:
|
|
|
|
- component redesign for starter-kit: who is tackling it? and how is the work reviewed?
|
|
|
|
- update the styling for starter-kit: what is the design to development workflow?
|
|
|
|
- small update to catch what we´re workin on, so we know
|
|
|
|
- Small update to catch what we´re workin on, so we know
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
### Meeting notes
|
|
|
|
#### Tooling & sharing of design assets
|
|
|
|
There doesn't seem to be a good way to share design assets between different tools such as Sketch, Figma etc. The best candidate for achieving this was exported SVGs, but each tool seems to have its own inconsistencies with the format, which puts a blocker on assets being imported to other tools.
|
|
|
|
|
|
|
|
The outcome is that the attempt to find a sharable format is put on hold, at least for now. As long as communication happens between designers and their ideas are shared, it is not an absolute necessity for the assets themselves to be common at this moment.
|
|
|
|
|
|
|
|
It will be good to use gitlab for disucssion and sharing of ideas and mocks, so that there is a written record of design decisions. As far as communication of design choices to developers is concerned, gitlab seems like a natural fit as well. The specifics of how assets and their technical details are communicated to devs is up to each organisation to sort out internally.
|
|
|
|
|
|
|
|
#### Pubsweet UI component library
|
|
|
|
We need to go through all the elements in the library and make sure they have sane default values and listen to the correct variables from the theme. We'll start with the elements that the group had gone through in the Athens meet, then keep tackling them in chunks that can be delivered to developers, so that they can be implemented in parallel.
|
|
|
|
@Nick is taking the lead on this
|
|
|
|
|
|
|
|
## previous meeting
|
|
|
|
*will be the logs for the previous meetings* |
|
|
|
#### Next IRL meeting
|
|
|
|
We discussed what the next in-person meeting agenda could look like.
|
|
|
|
Current candidates are:
|
|
|
|
* Reusable and sharable layouts
|
|
|
|
* Reusability of more complex components
|
|
|
|
* Sharing design ideas for reviewer discovery and assignment
|
|
|
|
|
|
|
|
It currently looks like the meeting will take place in May.
|
|
|
|
|
|
|
|
--- |
|
|
\ No newline at end of file |
