Pol Febrer Calabozo

In the first example what I didn't agree with is what you say about `xyz2`, with `xyz1` it was fine. The example that you give about SIESTA, then `pbc` should...

> And note, Siesta also has some problems with this, see https://gitlab.com/siesta-project/siesta/-/issues/129 I don't see it necessarily as a problem. These are two different situations, and the supercell shifts are...

> Could your Nodes flow be used to issue code when a variable changes (on-the-fly)? Hmm I guess, but it would probably be overkill, we could just introduce the check...

> The problem is that users coming from DFT codes are not used to this. So they expect it to work (seamlessly). And if sisl converts coordinates on-the-fly we should...

But we still didn't agree on the convention to follow 😅

I find it much easier to write documentation in notebooks. Could you give an example of the searching problem? The only problem that I noticed for now is that names...

Hmm that is plotly's javascript for the representation of the plot, not the notebook internals. Perhaps there are ways to avoid the search on that part. Also now the whole...

> which is annoying for the end user when searching for context ;) Yes, but that would also be there if the plot is generated with an ipython directive. I'll...

It's just that I don't find it better. In fact I find it harder to read and navigate, being all white, without any visual guides for the brain. But if...

It looks nice! I would remove the "to be filled". Just leaving a blank space (without even the user guide title) may be better. SIESTA's documentation was also full of...