[Docs] Expand Workspace and Design documentation to cover advanced topics

[zihanKuang]

This issue is to track the need to expand the documentation for Workspaces and Designs to address a number of advanced use cases and user questions raised during the review of PR #614.

The following topics need to be covered in the documentation to provide users with a deeper understanding of collaboration, permissions, and best practices.

1. When a design is transferred from one Workspace to the next, is design ownership affected? Who has access? What if the Workspaces are in different orgs?

2. What other users of a Workspace do with my design or view? Delete my design?

3. Can Workspaces contain private, public, and published designs?

4. What are best practices of organizing my workspaces? One per team? One per project? One for private designs only? A separate workspace for published designs (designs that are intended to be reusable patterns)?

5. How will I know if another user made changes to my design or view? Will I be notified? If there an edit history or audit trail?

6. If I share my private design with a user in a different org, can they share my design with other users?

7. My design is public and other users can edit my design, because of this. Is there a way to have my design publicly available, but read-only to other users?

8. When I import from a k8s manifest, helm chart or other type, a new design file is created. After making edits to my design, I can export my design in the same format from which I imported. Can I also download a copy of my original, unaltered file?

9. When I import from a k8s manifest, helm chart or other type, and choose to merge this file into an existing design, can I download my original file(s)?

10. Does workspace have space limitations or file count limitations?

These points may be incorporated into the existing "Workspaces" and "Designs" guides (Q&A) or may require new, separate documentation pages.

[kirti763]

Hii @zihanKuang I'd like to work on this

[zihanKuang]

Hii @zihanKuang I'd like to work on this

Thank you, @kirti763! All you need to do is practice these questions, then record his behavior. Feel free to ask me any questions you have.👍

[zihanKuang]

Hi @kirti763, this issue might require a bit more background knowledge. So I will take this on myself. Thanks again for your willingness to contribute! I'm sure there will be other issues where your can help with.