On 13-11-06 09:28 PM, S Page wrote:
On Tue, Nov 5, 2013 at 8:49 PM, Jared Zimmerman
<[email protected] <mailto:[email protected]>>
wrote:
I'm beginning to catalog behaviors here
https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Control_Library/Behavior
It sounds like you're going to write a new
<https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Patterns_and_components>
, but two levels down. If you can't adapt that, please Be Bold and move
it to /Old and move yours up.
I'm using the format of questions to capture behaviors, that won't
be the final state of this, but its helpful to capture some of the
places that will need clarity, like the control UI style guide
itself this will grow and change over time, as people interact with it.
Explaining behaviors is good, but the biggest boost to clarity will
come when designers add consistent text and names to the excellent specs
and mockups you've already built.
I love this graphic.
https://www.wikidata.org/wiki/Help:Statements#Glossary_of_terms
It makes sooooo much more sense of Wikidata's contents. (eg
https://www.wikidata.org/wiki/Q42 )
It might help to do diagrams like that for various aspects of many
products (such as Flow).
Consistent naming of features (whether we're talking to each other, or
writing documentation), is helped immensely by a diagram, at least for
some people.
Image is worth 1000 words.
Or you chop the specs up to fit these
wiki pages, which seems a lot of work. Maybe there's wiki markup to,
e.g. show a portion of page 3 of Agora_specs.pdf within a wiki page; I
couldn't figure it out and so took a cropped screenshot for
<https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Patterns_and_components#Buttons.2FActions>
, which sucks when you revise the original.
Clarity will also come when the LESS files use the same names and
reference wiki pages in their comments.
For example, the names in
<https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Control_Library>
like "Neutral, Progressive, Destructive, and Constructive" are very
helpful, but they're not in the mockups. I love your "Quiet action"[1],
but what does it look like? Is it a secondary action that doesn't have a
button outline?
I'm done for the night, so if you have questions to add, please do so,
The highest priority are the grid of buttons in Agora specs.pdf page 3
"Buttons" , we need good class names for their LESS implementation, and
decide what to do with the current mw-ui- classes. Let's nail 'em down
tomorrow.
The Behaviors terminology is different from its parent page
<https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Control_Library>.
Terms that appear in one and not the other include:
Behaviors:
primary, secondary, CTA, action buttons
action bar
ACL:
Quiet action, neutral null state.
action rail
[1] subtle Human League ♩♫ reference :-)
Cheers,
--
=S Page Features engineer
_______________________________________________
Design mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/design
_______________________________________________
Design mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/design
