Establish Backdrop Human Interface Guidelines

[jenlampton]

Backdrop should establish human interface guidelines. Once decided, these should be published for core (and hopefully contrib) to follow.

For example, Apple's HIG

Related: #1306

[dgoutam]

Initial design draft for HIG,

Appreciate suggestions/feedback.
Source code available at github

[quicksketch]

Nice! Could you put this into a branch with the name "gh-pages"? Then we could view it at http://dgoutam.github.io/backdrop-hig.

[dgoutam]

Pushed the first cut to http://dgoutam.github.io/backdrop-hig.

[jenlampton]

This is looking great :)

I set up HIG group within backdrop-ops, and added you to it @dgoutam. When you are ready, please see if you can transfer the project into backdrop-ops. If not, we can try to move it another way.

[dgoutam]

Moved to backdrop-ops.
Source code repo is available at http://github.com/backdrop-ops/backdrop-hig
gh-pages can be accessed at http://backdrop-ops.github.io/backdrop-hig/

[dgoutam]

Added new contents

• http://backdrop-ops.github.io/backdrop-hig/ui-ux-patterns/user-input/input-feedback/
• http://backdrop-ops.github.io/backdrop-hig/ui-ux-patterns/user-input/input-prompt/
• http://backdrop-ops.github.io/backdrop-hig/essentials/conceptual-model/

[dgoutam]

Added new Content

• http://backdrop-ops.github.io/backdrop-hig/ui-ux-patterns/user-input/constraint-input/

[mikemccaffrey]

I feel like there is a lot of work necessary to go back and document all of of the design patterns that we now take for granted after our years of working with Drupal. At some point we might want to have a dedicated documentation sprint to handle that big lift.

However, in the meantime, we should probably concentrate on documenting new design patterns that we are establishing as part of the [UX] tickets. In fact, we may want to require that to close any [UX] tickets we need not only a code push, but also a review and update to the HIG. Does that sound like a reasonable step to add to our workflow?

We may also want to think more about whether the HIG guide should be separate from the developer documentation on the API site. Supplying an interface is kinda a core part of building a new module, and if we separate the human component from the code, we end up in the same place as Drupal, with layers and layers of abstraction that contribute little to improve the daily administration and use of the website.

[jenlampton]

I've closed #1306 and makrked it as a duplicate of this one, but will reference from the parent issue here because there's a lot of good stuff in there.