> One major issue we've had though, which wasn't touched in this article, is inter-component communication among siblings. The way we typically handle somethin

> One major issue we've had though, which wasn't touched in this article, is inter-component communication among siblings. The way we typically handle something like this is by connecting components through a common ancestor. The default naive behavior of Panel apps is for linked components to share a "centralized state bag" (as one of the other comments calls it re: Redux), and updates to that state automatically cascade to all the components. It's a blunt, easy and lightweight way to propagate changes arbitrarily throughout an app, but it does get unwieldy as the state object gets big so we've ended up with some mechanisms for partial state-sharing to address this issue.