|
|
|
## July 25-26, 2018
|
|
|
|
|
|
|
|
### Agenda
|
|
|
|
During this pubsweet meet, some questions were raised:
|
|
|
|
|
|
|
|
- Should there be a pubsweet-design repo only for design questions? Jen stated that, for now, all the discussion that take place in the repo are more about dev implementations than proper design discussions and should happen in the pubsweet general repo. Are we agreeing to that?
|
|
|
|
- Should we have mockups for all the existing pattern that we can find in the stylguidist, as it seems that it's not easy to use for the designers? If so, where should they be?
|
|
|
|
- What would be useful to have for designers that we don't have yet? (svg or png mocks to share, designer FAQ and Best practices documentation? etc.)
|
|
|
|
- The pubsweet default theme (as known as pubsweet-UI) is now made from the styleguidist: when a dev implement a pattern, the theme switcher in styleguidist can show the same pattern with the default theme. This is useful for developers as they can build prototype app quickly. Should we have a proper UI-toolkit so a designer can make its own layout/mockups using the default theme? (would that be useful?)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Meeting notes
|
|
|
|
|
|
|
|
#### What we managed to do so far:
|
|
|
|
|
|
|
|
* Create a common vocabulary amongst developers and designers in the pubsweet community;
|
|
|
|
* Build a theming engine that let any designer build its own visual language, using variables and override;
|
|
|
|
* Start a default theme that can be used as is for new comers (Hindawi used the default theme to build the first prototype iteration of their app).
|
|
|
|
|
|
|
|
|
|
|
## June 26, 2018
|
|
## June 26, 2018
|
|
|
|
|
|
|
|
### Agenda
|
|
### Agenda
|
| ... | | ... | |