Feedback from doc review

> Add a welcome/introduction type article at the top of articles: orientate people first coming to that section, telling them what that documentation will allow them to achieve, who it is for, what it's about, etc. I'd advise putting a similar introduction type article at the top of all the sections, particularly:
>
> Hubs Documentation - Consider "Hubs user guide" or similar since all of this documentation falls under the branch of 'Hubs Documentation'
> Spoke Documentation - say what spoke is, who it is for, and what kinds of things you can do with it. What is the basic stuff people will want to try, and what are the most advanced bits to go onto later on
> For Creators - May not be clear who this document is for
> For Developers - Audience here may not be clear; it's also not clear if/how Hubs Cloud documentation is different than the general developer resources

Start by reviewing the Hubs Documentation, Spoke Documentation, For Creators, and For Developers sections to understand their current audience and structure. Done means each relevant section has a welcome or introduction article explaining who it is for, what it covers, and what readers can achieve, including the distinction between Hubs Cloud and general developer resources.

Written by the indexing model from the issue text.