[ ] Button (for input--submit.html.twig and for links, which are looking as buttons visually. UI Pattern)
[ ] Checkbox (analogue of checkbox.html.twig in drupal. Not UI pattern)
[ ] Icon (render of svg image from svg sprite. UI Pattern)
[ ] Radio (analogue of radio.html.twig in drupal. Not UI Pattern)
[ ] Select (analogue of select.html.twig in drupal. Not UI Pattern)
[ ] Text (for all text styles and links, which are looking like a text. UI Pattern)
[ ] Text field (for inputs text, date, tel, email, password, and so on. Not UI Pattern)
[ ] Textarea (analogue of textarea.html.twig in drupal. Not UI Pattern)
[ ] Throbber (for ajax in drupal, can be page throbber, like animated line on top of page, but also can be local circle icon, for example inside of ajaxed buttons. Not UI Pattern)
[ ] List (for ul, ol lists, UI PAttern)
Helpers:
[ ] Body scroll locker (Just a little script with external library dependency, helps us to lock scroll on any device - for example when burger menu opened, or dialog appeared, not UI Pattern)
[ ] Grid (grid with several settings by default. UI Pattern)
[ ] Slider (slider with several settings by default. UI Pattern)
Molecules:
[ ] Main navigation menu (an example of storybook's menu component. Analogue of menu.html.twig, but a bit customized -> so beginners will see how to create menu components. Not UI Pattern - because we don't have ui-patterns-menu module yet)
[ ] Checkboxes (analogue of drupal's checkboxes.html.twig. Not UI Pattern)
[ ] Radios (analogue of drupal's radios.html.twig. Not UI PAttern)
[ ] Details (analogue of drupal's details.html.twig. Not UI PAttern)
[ ] Fieldset (analogue of drupal's fieldset.html.twig. Not UI Pattern)
[ ] Form element (analogue of drupal's form-element.html.twig. Not UI pattern)
[ ] Form element label (analogue of drupal's form-element-label.html.twig. Not UI pattern)
[ ] Inline text content (for label and content, when it's splitted with : symbol between. UI Pattern)
[ ] Menu local task (analogue of drupal's menu-local-task.html.twig. Not UI Pattern)
[ ] Pager? (should we have this component by default? Not UI Pattern)
[ ] Table (analogue of drupal's table.html.twig + maybe for views-view-table.html.twig, but those template are different in drupal core, so maybe can be splitted on two different components? Not UI Pattern)
[ ] Branding (analogue of system branding block. Not UI Pattern)
[ ] Breadcrumbs (analogue of drupal's breadcrumbs.html.twig)
Organisms:
[ ] Header (Simple header)
[ ] Footer (Simple footer)
Templates:
Page (Analogue of drupal's page.html.twig. Can be just a test page where several components displayed at once. Can be UI Pattern, if we will use global panel with page layout)
Can be included:
[ ] Image style component. With all image styles defined with yml. That's the place where all image styles on entire project can be document / re-used somehow by drupal. BTW i have use this component already on 3-4 last projects and it was really helpful, when backender can quickly generate all image styles in drupal & generate configs from my yml file, using one command on console. To not waste the time to generate a lot of image styles manually
[ ] Responsive image group. Same as image styles, but for responsive images.
I suggest the following:
Atoms:
input--submit.html.twigand for links, which are looking as buttons visually. UI Pattern)checkbox.html.twigin drupal. Not UI pattern)radio.html.twigin drupal. Not UI Pattern)select.html.twigin drupal. Not UI Pattern)textarea.html.twigin drupal. Not UI Pattern)Helpers:
Molecules:
menu.html.twig, but a bit customized -> so beginners will see how to create menu components. Not UI Pattern - because we don't haveui-patterns-menumodule yet)checkboxes.html.twig. Not UI Pattern)radios.html.twig. Not UI PAttern)details.html.twig. Not UI PAttern)fieldset.html.twig. Not UI Pattern)form-element.html.twig. Not UI pattern)form-element-label.html.twig. Not UI pattern):symbol between. UI Pattern)menu-local-task.html.twig. Not UI Pattern)table.html.twig+ maybe forviews-view-table.html.twig, but those template are different in drupal core, so maybe can be splitted on two different components? Not UI Pattern)breadcrumbs.html.twig)Organisms:
Templates:
page.html.twig. Can be just a test page where several components displayed at once. Can be UI Pattern, if we will use global panel with page layout)Can be included: