The Design Initiatives main purpose is to build a new theme for Drupal 8 and as part of this initiative we are preparing a Design Brief. The brief will be part of a "Designers Toolkit" which also includes a set of wire-frames. The brief itself comprises of two parts - a set of documents outlining Drupal core output (to support and clarify the wire-frames) and a Use Case Brief. Its the last bit I want to talk about here and open up discussion on. In essence what should this use case be?

Building a Drupal project using git is different than building Drupal itself, and requires its own workflow. I've been kicking ideas back and forth with Sam Boyer lately about how to make this process take advantage of all the Git power, but also be newbie-safe and as frictionless as possible. I think what we've come up with is pretty good: there's even code written! The process I am going to explain allows the following:

• Git-based updates for Drupal core and contrib
• The ability to patch/tweak core/contrib without the complexity of vendor-branches
• Portability for local development or Git-based deployment
• Unrestrained custom development: feature branches, tags, multiple repos
• Safe patterns that minimize conflicts and provide a clear resolution process

Pretty cool, eh? Expect a larger manifesto post from Sam in the near future, but for now here's where we are heading.