The toggle button is currently displayed automatically at a given fixed position in mobile resolutions. That couples the whole layout with a specific size and makes assumptions about the existence of a header where content is placed in concrete locations.
Instead, it would be good to extract the button into its own component, and make it "notify" the sidebar to toggle via context.
Applications would have to wrap both <ShlinkWebComponent /> and <ToggleButtonWhatever /> under a common context for this to work, but they would have more control over where and when to display said button.
The toggle button is currently displayed automatically at a given fixed position in mobile resolutions. That couples the whole layout with a specific size and makes assumptions about the existence of a header where content is placed in concrete locations.
Instead, it would be good to extract the button into its own component, and make it "notify" the sidebar to toggle via context.
Applications would have to wrap both
<ShlinkWebComponent />and<ToggleButtonWhatever />under a common context for this to work, but they would have more control over where and when to display said button.