More refined categories for components

[adamkudrna]

Like this:

• Actions
  • Button
  • TextLink
• Inputs
  • CheckboxField
  • FileInputField
  • Radio
  • SelectField
  • TextArea
  • TextField
  • Toggle
• Surfaces
  • Card
  • Paper
• Overlays
  • Modal
  • Popover
• Layouts
  • ButtonGroup
  • FormLayout
  • Grid
  • Toolbar
• Miscellaneous
  • Alert
  • Badge
  • Table
  • Tabs
  • Text
  • ScrollView

[adamkudrna]

Relates to #314.

[adamkudrna]

Current Miscellaneous section:

• Miscellaneous
  • Alert
  • Badge
  • Card
  • Modal
  • Paper
  • Popover
  • ScrollView
  • Table
  • Tabs
  • Text

… could be organized:

• Data Display
  • Badge
  • Table
• Feedback
  • Alert
• Surfaces
  • Card
  • Paper
• Navigation
  • Tabs
• Overlays
  • Modal
  • Popover
• Utilities
  • ScrollView
  • Text

Or, to avoid single-child categories:

• Data Display
  • Badge
  • Table
• Surfaces
  • Card
  • Paper
• Overlays
  • Modal
  • Popover
• Miscellaneous
  • Alert
  • ScrollView
  • Tabs
  • Text

Or at least:

• Surfaces
  • Card
  • Paper
• Overlays
  • Modal
  • Popover
• Miscellaneous
  • Alert
  • Badge
  • ScrollView
  • Table
  • Tabs
  • Text

[mbohal]

I like the Or at least: version the best.

I think the Data Display category is unclear as I would look there for Text and ScrollView as well.
I'm quite opposed to the single-child categories.

[adamkudrna]

Well, you feed all components with data. But there is a difference:

• Data Display components provide visual form for specific kind of data: numbers, table data, … Even card designed to display user data could fit this box.
• Utilities enhance components in a way, or help you solve some tricky situations, e.g. when the data does not fit the component.

[mbohal]

@adamkudrna I understand what you mean, yet I still find the Data Display category confusing. If it was up to me I would not use it.

You decide, but please lets avoid single child categories.