2019_03_01_Kirby Guild Meeting Summary

This page contains a meeting summary from the Kirby Guild meeting, held on March 1st, 2019.

Reiteration from last meeting

• Meeting notes and all issues are primarily tracked in Github.
• Only a few issues remain in Trello, more or less all of them are now in Github Issues.
  • Everything is transparent
  • Easy to differentiate enhancement from bugs, by using labels

Cookbook

• Jakob has spoken to Mads, the UX team also thinks in Components, very much.
• Linking to a versioned design, able to see what Kirby supplies (are components stale or up-to-date)
  • Each component has their own component, the Kirby package its own composite version (release version).
• Get inspiration from shopify, or even more specific as https://clarity.design does it.
• Link to zeppelin.io (Sketch-designs) from the cookbook
• (overstreg) Tom creates a design for buttons
  • Big challenge is DesignIt, hasn’t delivered a “fully done“-component.
• Attacking Card as first component
  • Get it completely done
  • Link to zeppelin
  • Code samples for HTML, both for Web and {N}
• New feature #124 - Task for “Component status”-representation in Cookbook
• New task #125 – Task for clarifying how-to use Highcharts (is peer dependency enough)
• New tasks #126 - Tom will iterate on naming of Colors and Buttons

Other tasks

• Jonas creates a few new templates for clarifications, UX tasks etc.
• Jonas will look at creating project board (to have a prioritized list of issues – a Kanban board?)
• Jakob create a draft version of review guide-lines: “New task #127 - Create Review guide-lines” – let’s all add to this
• Alexander looks at contribution guide-lines: “New task #128: Create “How-to contribute”-file”

Topic(s) for next meeting

• Is Kirby-list implemented correctly on native?
  • Issues adding Kirby-list in ScrollView