Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contribute the next evolution of the IBM Watson Design Guide #449

Open
4 tasks
hackygolucky opened this issue Aug 27, 2015 · 6 comments
Open
4 tasks

Contribute the next evolution of the IBM Watson Design Guide #449

hackygolucky opened this issue Aug 27, 2015 · 6 comments

Comments

@hackygolucky
Copy link

A few of us have been tasked with building the next evolution of the Watson Design Guide as it currently stands at v1.1.0.

We will:

  • Build on reflecting the cohesion of Watson products
  • Refine communicating visually, with content, and with the structure of the website that the Watson Design guide is a supplement to the IBM Design Language guide
  • Incorporate a feeling of texture and pattern
  • Updates to readme and any other docs necessary for continued ease of contribution

Proposed site map revision:
image

Proposed visual design revision:
image

There's certainly more comps to view but I didn't want to bombard the issue with a ton of hefty image files.

@poofichu
Copy link
Contributor

Where's the pattern library?

I would love if you guys would reach out to us to go over this.

@Snugug
Copy link
Member

Snugug commented Aug 27, 2015

I'm not sure that Framework and Resources are the right headings for those sections. I know it's what the Design Guide uses, but they seem counter-intuitive to the people actually going to use them. Has there been user testing around those names?

@hackygolucky
Copy link
Author

@poofichu the intention is for the pattern library to fall under Resources, but potentially called something else.

@hackygolucky
Copy link
Author

@Snugug We've gotten initial feedback on content from 4 sessions with visual designers. There was not any negative feedback on the headers. We haven't yet tested with developers.

We may scope this back to be focused on the visual designer at first and use the existing content for developers until we're able to focus on the developer-as-user for a next step. This is a first draft of the next iteration. I'll update any changes addressing scope of user(s) as it happens.

@Snugug
Copy link
Member

Snugug commented Aug 27, 2015

Thanks for the update. It'd be if you added any user research you had to the wiki so we can all keep track of it.

@hackygolucky
Copy link
Author

Oh that's very good to know. I'm still familiarizing myself with all of this. Noted and will track down!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants