Expected Behavior

Organize the storybook stories by type of component. For example Box is a type of Layout component. All the Layout components should be grouped together like they are in the documentation https://v2.grommet.io/components.

Actual Behavior

The stories are organized alphabetically by component.

URL, screenshot, or Codepen exhibiting the issue

![image](https://us

The DatePicker component is already created and it's functional, but it was written some time ago and it can be refactored (migrating from class-based to hooks). In order to achieve a good result, we also need a good test coverage.

Running storyb

Just happened to notice this while working on some other code. I'm moving a utility function out of /types and into its own /utilities file.

• I have searched the issues of this repository and believe that this is not a duplicate.

Version

1.11.10

Component

Nav

Environment

Chrome Latest

Reproduction link

Steps to reproduce

期望可以透传s

Is your feature request related to a problem? Please describe.
I use theme-ui on daily basis on personal and work projects. The documentation is quite large and I just want to remember something that I used before so I navigate the whole docs to get it.

Adding search in docs page will make it easy to remember things fast instead of navigating the documentation.

**Describe the solution

The generic codesandbox link on the homepage should also come with sass support wired up so that consumers can easily use EUI's Sass mixins.

An example of a codesandbox link with Sass working (though a lot of package are out of date): https://codesandbox.io/s/testing-sass-useforward-cm2rl

![image](https://user-images.githubusercontent.com/4188087/97337604-7d155d80-184e-11eb-8efd-3a86e387a0f

Proofreading from native speakers wanted. Review and comment on this PR 🙏.

Hi, I am using atomize for a toy project. I noticed that the collapse atom is not very snappy in it's animation, I'd like to speed up the animation. How to do this? Thank you!