Skip to content

Organize storybooks better #2

@ferrine

Description

@ferrine

IN the storybooks of graphene there are old micro storybooks that are outdated, the intention is to show only carbon components, foundations, all the other storybooks are from the past when there was nothing structured

priv/storybook/
├── basic_components (should be revisited if it makes sense to keep it separate and include other basic components there)
│   └── table
├── carbon_components
│   ├── ai_skeleton
│   ├── checkbox
│   ├── contained_list
│   ├── data_table
│   ├── date_picker
│   ├── file_uploader
│   ├── fluid_number_input
│   ├── fluid_search
│   ├── fluid_select
│   ├── fluid_time_picker
│   ├── header_menu_button
│   ├── list
│   ├── notification
│   ├── overflow_menu
│   ├── pagination
│   ├── popover
│   ├── radio_button
│   ├── search
│   ├── select
│   ├── side_panel
│   ├── skeleton
│   ├── slider
│   ├── tearsheet
│   ├── tile
│   ├── time_picker
│   ├── toggle
│   ├── tooltip
│   ├── tree_view
│   └── ui_shell_variants
├── components (obsolete)
├── foundations
├── generated
│   ├── core
│   └── product
└── product_components
    ├── checklist
    ├── guide_banner
    ├── options_tile
    ├── patterns
    ├── story_assets
    └── tearsheet

Moreover I found that in the graphene.scss storybook css is included which is not good separation of concerns, should be revisited and organized better too

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions