Design-meetings.md

-## April 12, 2018
-
-- Decide on the use of naming convention with gridUnit on the starter-kit (check below)
-- Subgrid: decide if we stick to the smaller unit grid system or on a line-height based grid.
-- Update on buttons (#19) and discuss next element to design. 
-- update on buttons: @julientaq can show example of states for the buttons and how it could be implemented on the theme if we all agreed. (simple `box-shadow` on focus and hover on clic).
-- Frequency of design meetings: We have had just over a months worth, now might be a good time to evaluate how often we need them.
-- Accessibility checklist: eLife will be meeting A and AA requirements from this list https://www.w3.org/TR/WCAG20/ when sharing back to the vanilla kit do we all agree that this suitable for now?
-- Variables: Are these suitably locked down for eLife to build against?
-- eLife: component build next steps
+## April 17, 2018
+
+### Agenda
+* Decide on the use of naming convention with gridUnit on the starter-kit (check below)
+* Subgrid: decide if we stick to the smaller unit grid system or on a line-height based grid.
+* Update on buttons (#19) and discuss next element to design. 
+* Update on buttons: @julientaq can show example of states for the buttons and how it could be implemented on the theme if we all agreed. (simple `box-shadow` on focus and hover on clic).
+* Frequency of design meetings: We have had just over a months worth, now might be a good time to evaluate how often we need them.
+* Accessibility checklist: eLife will be meeting A and AA requirements from this list https://www.w3.org/TR/WCAG20/ when sharing back to the vanilla kit do we all agree that this suitable for now?
+* Variables: Are these suitably locked down for eLife to build against?
+* eLife: component build next steps
+
+### Meeting Notes
+* Whether we use subGridUnit or gridUnit is more of a developer question, as long as we provide a way to stay on the grid.
+* Button discussion has been closed on gitlab, so it's up to Yannis to implement it on the styleguide now.
+* The driver for next elements to work on will be organisational needs from now on (instead of collectively deciding on a set), as we're all trying to deliver software at the moment.
+* The process for changes or introduction of new elements will be to show the new/changed element to the design group, have it pass and get the devs to introduce these changes into the styleguide. The important part would be to avoid prolonged discussions about minor points. We can always introduce more changes later.
+* Variables seem to be satisfactory to everyone so far, so we can safely consider them good for use.
+* Accessibility standards checklist will be the list posted above by Nick.
+* The frequency of the design workgroup meets from now on will be every other week, so that there is more to show and we don't end up stretching people's already tight schedules.
+* The phrase "starter kit" is from now on **banned**. Use "pubsweet ui" or "styleguide" instead.
 
 ## April 3, 2018