Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">Your style guide is an experience</h1> <div class='date'><time class="dtstart dt-start" title="2015-05-21T18:30:00" datetime="2015-05-21T18:30:00">Thursday, May 21, 2015 from 6:30</time>–<time class="dtend dt-end" title="2015-05-21T20:30:00" datetime="2015-05-21T20:30:00">8:30pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202394689'><span class='fn org p-name'>eBay Community Lounge</span></a> <div class="adr p-adr h-adr"> <div class="street-address p-street-address">1400 SW 5th Avenue, 3rd Floor</div> <span class="locality p-locality">Portland</span> , <span class="region p-region">OR</span> <span class="postal-code p-postal-code">97201</span> <div class="country-name p-country-name">US</div> (<a href='https://maps.google.com/maps?q=1400%20SW%205th%20Avenue,%203rd%20Floor,%20Portland%20OR%2097201%20US'>map</a>) </div> </div> <div class="description p-description"> <p>Whether you call it a living style guide, pattern library or a design system one thing remains true about the style guide; it in itself is an experience. It can serve as a contract, a learning tool, and single source of truth for not just engineers but for designers and product owners. An understanding of each stakeholders' needs will better inform the design and process fit of your style guide.</p> <p>In this talk UTI Worldwide UX Architect Edward Irby will explain the five basic factors of successful style guides.</p> <p>• Workpace</p> <p>• Components</p> <p>• Animations & Interactions</p> <p>• Namespace</p> <p>• Utility Styles</p> <p>He'll then go into detail about finding process fit, dealing with uncertainty (unknown/changing codebases), and imbuing your style guide with intent.</p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://www.meetup.com/pdx_UX/events/222054664/">Website</a></li> </ul> </div>