Friday 27th May, 2016
3:40pm to 4:20pm
It will be a walk through Origami, with it's key parts described in contrast with other similar components systems created elsewhere. An alternative talk title could be "things Origami could learn from other components systems"
I'll look at the methodologies for deciding what gets to be a component, and compare this to more pattern-library type approaches (such as the atomic-design method used at Future Learn)
I'll look at how various teams have approached documentation and talk about why Origami do this badly and how they can improve it.
I'll compare how Origami handles delivery of its components to browsers, and contrast it to how GDS and Lonely Planet have approached this.
By the end of the talk, the listener should understand a bit about how large companies like the FT deal with front end development at scale, and they will hopefully have some ideas about front end architectures to take back to their own worlds.
Sign in to add slides, notes or videos to this session