Chris Sewell

Heya, I'm afraid sphinx-panels is now deprecated for sphinx-design: https://sphinx-design.readthedocs.io/en/furo-theme/get_started.html#migrating-from-sphinx-panels Your welcome to check out that package, and see if the same can be applied

No this directive **is** for the long form content, not the tooltips. Although I mention the three styles, really I think this directive is most suited to (1), whereby you...

Thanks @jorisvandenbossche yes sounds reasonable 👍 I'll have a think about the issues you mention and get back to you (feel free to ping me if I forget lol)

This will essentially be closed by https://github.com/executablebooks/sphinx-design, where it has already been fixed

This will essentially be closed by https://github.com/executablebooks/sphinx-design/issues/6

Note styles could also be used for panels, and additional "project-wide" styles could perhaps be added in `conf.py`, e.g.: ```python dropdown_styles = { "my-style": { "container": ["mb-2"], "title": ["bg-primary", "text-center"],...

Thanks @CAM-Gerlach, yep that sounds like it should be quite possible 👍

It's not a one-to-one mapping, but there are certainly some extra aspects that could go into panels: primarily the ability to turn the entire card into a clickable link (could...

What would be the "ideal" UI/UX for this? i.e. what would the content look like closed/open, where does the user click to collapse/expand? In [sphinx-togglebutton](https://sphinx-togglebutton.readthedocs.io/en/latest/#the-toggle-directive):  In jupyter-lab: 

Note that, if this was to fully supersede `sphinx-togglebutton`, it would also need to cover the use case of adding togglability to existing containers: https://sphinx-togglebutton.readthedocs.io/en/latest/#toggling-content-by-adding-classes. This is particularly neccessary for...