The structure of QDS documentation makes it difficult for users to find what they are looking for

Currently we have a mix of conceptual level documentation and reference documentation. Thing is, the modern world expects more use-case based instructions and less "guide book" instructions.

Documentation needs to cater situation where

• user is after a single component and reference documentation of it
• user wants to see example cases of the component in question

Component is not just 'pure' QML item but also an advanced, functional QML item.