Demetris Roumis

Great write-up! 'hvsampledata' would make it a bit more clear that this is data not about any holoviz thing, but a sample dataset to work with along side holoviz things....

minor comment about docs, but either way 👍

I don't think merging this depends on exposing HEPs on the website. It certainly wasn't a blocker for HEP1. Let's go ahead and merge this and then continue the website...

1. Improve the structure of Panel's technical reference material (primarily the API reference and component gallery sections-[#4305](https://github.com/holoviz/panel/issues/4305)) 2. Improve guidance on tool selection as part of the getting started experience...

It's encouraging that this discussion is happening and I hope it leads to cleaning up the reactive story. Creating reactive dependencies always trips me up, especially when I'm working across...

@maximlt.. hmm maybe instead of tap, a more useful example would be the following, where the `.selection.x` is the x index of the data currently selected with a selection-type tool....

Indeed, we spoke a bit about a new top-level nav organization for HoloViz.org during a meeting about a month ago. Here is what was proposed, which seemed at the time...

This would definitely be a great benefit to the community. Here are some related data from our user survey that may inform the course of action. I think it makes...

superseded by https://github.com/holoviz/holoviz/issues/394

Thanks @cbrnr ! To reiterate, we welcome any questions or requests. Also, just going to drop the linked preview here for convenience: https://github.com/holoviz-topics/neuro/assets/6613202/de4783da-5bef-496c-8b09-a280d742eff4