Black Lives Matter. Please consider donating to Black Girls Code today.
Dash HoloViews is now available! Check out the docs.

Conceptual boundary between Plotly Dash layouts and components?

Hi friends,

I’m trying to evaluate whether I should implement my re-usable functionalty/dashboard as a custom component or a layout.

I’m looking for a more or less exact definition of where I should draw the boundary between a (React) Component and a Python (Layout).

Can you give some advice or rule of thumb of when to go for one or the other?

Best & Thanks! :slight_smile:

Trying to rephrase the question:

I’m trying to wrap my head around the conceptual boundary between a layout and a component.

I.e. in which cases should I make something a re-usable, custom component using ReactJS (as described under https://dash.plotly.com/plugins ) and in which cases should I make a layout or part of it re-usable by wrapping it into a plain old Python function (as described in the Reusable Components section under https://dash.plotly.com/layout ). Any kind of input or rule of thumb would be greatly appreciated. :slight_smile:

Main reason behind my question is that I want to write a library of re-usable components that I can use in many different (Python) dashboards. Now I’m wondering whether I should rather write them in ReactJS or Python.