Currently, when developing a widget in Widgetbook, whenever a change is made hot reload causes the Widgetbook to reset to the "home" page, and you're forced to open the widget again to see the changes. This is very annoying when you're making a lot of changes during the development process and want to have a fast feedback loop. Instead, could it be made so that Widgetbook reloads without losing state (i.e whatever story's currently opened)? I've attached a video of an example.

Hey folks, a feature suggestion is having access to the documentation of widgetbook in the main page of the website(widgetbook.io), it could be only a button or anything like that. It would be easier for those who want to access the documentation, that actually only have access through docs.widgetbook.io

Enums exposed via knobs