[docs] Toolpad docs part 1

[bytasv]

Partial implementation for #834
Preview: https://deploy-preview-859--mui-toolpad-docs.netlify.app/toolpad/getting-started/overview/

• I have followed (at least) the PR section of the contributing guide.

1. Started working on docs according to notion page structure - got Introduction and Quickstart pages
2. Merged Setup steps into Quickstart as that was basically one paragraph on it's own page
3. Added step-by-step guide both to build first app and to deploy it
4. Connecting to data sources - Connections, Query, Fetch, Function ✅
5. Data binding section ✅

---

• 🔗 Overview
• 🔗 Quickstart
• 🔗 Connecting to datasources - Queries
• 🔗 Connecting to datasources - Connections
• 🔗 Connecting to datasources - Fetch
• 🔗 Connecting to datasources - Function
• 🔗 Connecting to datasources - Postgres
• 🔗 Data binding

[render]

Your Render PR Server URL is https://toolpad-pr-859.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cc4am2b19n0agdht37vg.

[oliviertassinari]

Happy to see more documentation :)

Closes #834

I'm not sure about how much work this represents. If it's a big effort, I think that we should change this to: "One step toward #834". So we can have small PRs that we merge incrementally.

Regarding who should review this PR, would it make sense to have, Prakhar & Jan for the product side and maybe Sam for the technical writing dimension in the first few PRs to the point where most of the best practices have been shared?

[prakhargupta1]

A couple of suggestions for consideration. Should we replace:

1. Toolpad app with Toolpad
2. Component's library with Component drawer
3. Application editor with Canvas
4. Properties editor with Properties pane or right pane
5. Instance editor with left pane

based on:
-single word > two words
-Along with the name, if we could help users visualize then it would be better

[Janpot]

5. Instance editor with left pane

alternatively:

• project hierarchy
• explorer (They use this in vscode)
• navigation pane
• outliner (blender)

[bytasv]

@oliviertassinari

I'm not sure about how much work this represents. If it's a big effort, I think that we should change this to: "One step toward #834". So we can have small PRs that we merge incrementally.

I can definitely do that, I'm just not sure how fast we can merge this one then so I wouldn't blocked to open new ones. Or maybe this can be merged and still kept for feedback that I could deliver in a follow up PRs?

Regarding who should review this PR, would it make sense to have, Prakhar & Jan for the product side and maybe Sam for the technical writing dimension in the first few PRs to the point where most of the best practices have been shared?

Yeah, I think it makes sense, in general the more people look the better as I might have missed some things, might have explained something how I understand but maybe it's not how it actually is, etc...

---

@prakhargupta1

Component's library with Component drawer

I'm wondering if we are sure that the UI for that will not change? Are we going to keep using "drawer" in the future as well? I was thinking about more "universal" name that would not depend on the implementation 🤔

For no.5 - I like Jan's proposal for "Explorer" or basically looking for analogy in other products. Quick search gave me this:

Seems that "explorer" in VS code refers only to files explorer, in our case it might be instance explorer (short version just "explorer") but maybe we should use more generic one "Sidebar"? 🤔

I see following options that could be used:

1. Left pane and Right pane
2. Explorer (left) and Properties (right)
3. Left sidebar and Right sidebar (this is maybe bit more explicit as being on the "side" compared to pane 🤔 )

More examples:

xcode:

one more for xcode (navigator and inspector sounds nice as well)

It also got me thinking about this

Application editor with Canvas

Seems that Canvas isn't commonly used, so maybe just keep Editor?

[bytasv]

Hey @samuelsycamore is this good to be merged?

[samuelsycamore]

@bytasv I'm good to merge this as it is, mainly because this PR has gotten massive and I don't want to add 100 more comments to it! 😅 I would still like to review the "Connecting to datasources" pages, but I can open separate PRs and tackle them one by one once this is wrapped up here.

[bytasv]

Thanks @samuelsycamore ! See what's the easiest way for you to deliver feedback, you can comment on this PR or open new one, lemme know if I can assist somehow