All demos have been converted to stories, with a few caveats.
Global CSS stories are basically straight ports of demo version as these will need to be refactored when moving global styles into applicable components. As for previewing changes to these styles, the stories will facilitate this need.
Auth, Guard, and Hal demos are awkward to represent as stories since their functionality is dependent on running in an environment that supports proper authentication (SSL, proxied domain, etc.). Also, the current state of the docs for these services are sparse, hard to follow without context, and their functional demo code doesn't reflect what is instructed or is missing functional example for some instructions. Help from someone with more expertise in usage of these service would be appreciated.
BaseModel story is pretty much just documentation.
Navigation related stories whose components rely on router directives (Header stories, Tabs) needed to be setup with routing that can interfere with storybooks hot-reload of content iframe (Storybook's iframe app doesn't usually have routing setup.)
All demos have been converted to stories, with a few caveats.