schumpert / Scott Schumpert

There are no people in schumpert’s collective.

Huffduffed (2)

  1. Faster Design Decisions with Style Tiles

    With responsive design designers need to rethink the process they go through to work with clients and developers to create successful visual designs. Rather than creating traditional comps, style tiles are a deliverable that help you to communicate with your client, establish a visual language and work iteratively with developers. In this presentation, Samantha will explain how to reinvent your process to leverage Style Tiles as a deliverable.

    Samantha Warren is an experienced designer, speaker, and writer who leverages a diverse background in artistic mediums to create compelling and functional web experiences. Focused on designing for content, she is passionate about using the web as a vehicle to tell compelling stories while creating accessible user-experiences. She has been published in .net Magazine and has presented at various industry events, including Design Day in Pittsburgh Pennsylvania and the South By Southwest Interactive Festival in Austin Texas.

    Currently Samantha is the Design Director at Phase2 Technology where she uses her past experience working with brands like National Geographic and Choice Hotels International to help non-profits, publications, and associations tell their stories online.

    In her personal time she talks about design and the web on her blog, BadAssIdeas.com and spends time with her cross-eyed cat, Grace.

    http://schedule.sxsw.com/2012/events/event_IAP10133

    —Huffduffed by schumpert

  2. CSS for Grown Ups: Maturing Best Practices

    In the early days of CSS the web industry cut its teeth on blogs and small personal sites. Much of the methodology still considered best-practise today originated from the experiences of developers working alone, often on a single small style sheet, with few of the constraints that come from working with large distributed teams on large continually changing web projects.

    The mechanics of CSS are relatively simple. But creating large maintainable systems with it is still an unsolved problem. For larger sites, CSS is a difficult and complex component of the codebase to manage and maintain. It's difficult to document patterns, and it's difficult for developers unfamiliar with the code to contribute safely.

    How can we do better? What are the CSS best practises that are letting us down and that we must shake off? How can we take a more precise, structured, engineering-driven approach to writing CSS to keep it bug-free, performant, and most importantly, maintainable?

    http://schedule.sxsw.com/2012/events/event_IAP9410

    —Huffduffed by schumpert