search

carbon-design-system / carbon-for-ibm-dotcom

Carbon for IBM.com is based on the Carbon Design System for IBM
https://www.ibm.com/standards/carbon/
Apache License 2.0
264 stars 157 forks source link

Glossary #203

Closed jeffchew closed 4 years ago

jeffchew commented 4 years ago

LARAHANL created the following on Mar 05:

Let's define some of the commonly used terms from the design perspective so that when designers work with other teams and disciplines we can be clear.

Main doc is here

Deliverables

Batch 1

Batch 2

Batch 3

Acceptance Criteria

Additional information

Audit of other IBM design systems

Original issue: https://github.ibm.com/webstandards/digital-design/issues/610

jeffchew commented 4 years ago

On Apr 30, larahanlon commented: Currently collaborating with Kristen Kogachi to create a team-wide, sharable glossary. See this Boxnote for WIP definitions.

Next steps:

jeffchew commented 4 years ago

On May 24, Wonil-Suh1 commented: I suggest that we divide this into smaller chunks that we can focus on over sprints. The goal for each batch would be to focus and define the given terms in the batch, and get agreement.

Batch 1: fundamental building blocks

Batch 2: solving complex problems

Batch 3: higher level

Sprint 13 and on: let's see where we are and decide.

jeffchew commented 4 years ago

On May 24, Wonil-Suh1 commented: Converting to an epic according to the table and will add an issue for each batch so that we can work on each and close them out in sprints.

jeffchew commented 4 years ago

On Jun 06, larahanlon commented: 🤔 What is the outcome of all of this? Where will this content live?

Here's some inspirations from InVision! https://www.invisionapp.com/design-defined/

screen shot 2019-06-05 at 4 32 18 pm
jeffchew commented 4 years ago

On Aug 20, larahanlon commented:

Team, this looks great. Some nit picky items:

  1. There has been a sustained debate about this model v. the atomic design model. Can you please explain the relationship of our stuff to the elements of atomic design so we can avoid that debate again?
  2. For Core Components, please explain a bit more on the Carbon philosophy of core components, why there are so few of them, etc
  3. Examples of patterns provided looks more like TYPES of pattern categories, not examples of actual patterns. e.g. a workflow is a category. I would expect us to then say that Buy is sub-category, and that there are 3-5 patterns for Buying on IBM.com (e.g. 1st time purchase; Add Seats or "Buy More", etc etc.) . I see us go back and forth on the definition of patterns all the time, so I'd like us to get to a tighter definition here.
  4. Theme. Why aren't we discussing Expressive and Productive Theme here? That's critical to the new architectural relationship with Carbon. We have to nail this one and be clear on how it works.
  5. Module. Please add more than one description.
  6. As i'm reading this, it's clear that while this glossary is a great foundation for the team, we need a pictorial representation of a page to more eficiently describe these things, something like "all the things that form a page."
  7. And finally, let's make sure that we nail the difference between a page and a template.
jeffchew commented 4 years ago

On Sep 03, larahanlon commented: @Wonil-Suh1 how do you feel about creating new issues for the next sprint? I think we could address some of Elliott's feedback without too much labor. We've already made a start on defining module, theme, band – they just need some elaboration. We could also tackle page template with Web Simplification.

stale[bot] commented 4 years ago

We've marked this issue as stale because there hasn't been any activity for 30 days. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.