Components structure in deerflow codebase - Part 1.1

Inspired by BulletProof React , I applied its codebase architecture concepts to the bytedance/deerflow . This article focuses only on the components structure in bytedance/deerflow codebase . Prerequisite Components structure in Deerflow codebase — Part 1.1 Approach The approach we take is simple: Pick a route. Locate this route in DeerFlow codebase. Review how the components are imported and organized. We repeat this process for 3–4 pages to establish a common pattern, see if there’s any exceptions. In this part 1.1, we review the components structure in the DeerFlow’s demo workspace feature. When you visit https://deerflow.tech/ and open any case study, you will be taken to this route — https://deerflow.tech/workspace/chats/4f3e55ee-f853-43db-bfb3-7d1a411f03cb I got curious about how the components behind this feature are organized and I looked at it’s source code. We will look at components structure in: ChatsPage WorkspacePage ChatsPage ChatsPage shows a list of chats. In ChatsPage