<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Andrew Denty</title>
    <description/>
    <link>https://speakerdeck.com/andrewdenty</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/andrewdenty.rss"/>
    <lastBuildDate>2017-12-03 07:05:30 -0500</lastBuildDate>
    <item>
      <title>The road to faster mock-ups: How we built and shared our design system - UX Cambridge 2017</title>
      <description>Design systems help us design consistent, joined up experiences across different products and platforms. With many designers working across a company, how do you easily share your design system so they’re each working with the latest version and not duplicating work? 

This session is a case study aiming to give an overview of how we have used our design system, Honeycomb. Most talks on design systems focus on building a web toolkit, or library, with a bunch of developer ready components. But I want to show how we have created a number of resources for designers to speed up how they create designs before they hand over to developers. 

We have used tools such as Sketch and Brand AI to build a library of components, which makes it really easy to create and change mockups. We typically use these mockups to test designs with end users before building.</description>
      <media:content url="https://files.speakerdeck.com/presentations/6781b4e0853a48f9af43dc529dfff4f0/preview_slide_0.jpg?9098729" type="image/jpeg" medium="image"/>
      <content:encoded>Design systems help us design consistent, joined up experiences across different products and platforms. With many designers working across a company, how do you easily share your design system so they’re each working with the latest version and not duplicating work? 

This session is a case study aiming to give an overview of how we have used our design system, Honeycomb. Most talks on design systems focus on building a web toolkit, or library, with a bunch of developer ready components. But I want to show how we have created a number of resources for designers to speed up how they create designs before they hand over to developers. 

We have used tools such as Sketch and Brand AI to build a library of components, which makes it really easy to create and change mockups. We typically use these mockups to test designs with end users before building.</content:encoded>
      <pubDate>Fri, 08 Sep 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/andrewdenty/the-road-to-faster-mock-ups-how-we-built-and-shared-our-design-system-ux-cambridge-2017</link>
      <guid>https://speakerdeck.com/andrewdenty/the-road-to-faster-mock-ups-how-we-built-and-shared-our-design-system-ux-cambridge-2017</guid>
    </item>
  </channel>
</rss>
