Optimizing Canvas Management: Proposed Folder-Based Organization for Multi-Stage Project Coordination

I hope the management of canvases can be optimized. For example, could we add a folder-like management unit for the current canvases? Currently, canvases can be added to a knowledge base, but not all canvases are suitable for a single knowledge base.

For instance:
I am working on an OA system, where the requirements, project initiation, bidding, procurement, design, development, project management, and promotion are all managed in different canvases for each phase. The knowledge base for the OA system might only focus on the management of the OA business itself, such as the processes involved, which ones require co-signatures, which ones require or-signatures, which ones are for issuing documents, and which ones are for receiving documents. Therefore, only the canvases related to requirements and design would be suitable for the OA knowledge base, while the others would not.

If there are too many canvases, it will inevitably lead to management chaos. I hope this can be considered holistically.

It's not that having all project-related information in one canvas is bad, but too much information can be confusing, and having too many nodes in a canvas can also affect performance. So, could the structure management of canvases be optimized? Let's discuss this together.

No files, tests, or entry points are named. Start by locating the existing canvas and knowledge-base management flows, then clarify the folder model and scope with maintainers. Done would require an agreed structure and documented behavior for organizing canvases across project stages.