The tutorials of Qiskit Nature have long been "subpar" and do not cover the full breadth of its capabilities.
I think that we need to make our users more aware of that fact or (at least) acknowledge that we are aware of this ourselves in some form or another.
In this PR, I am putting forward a proposal to take care of this.
Basically, I am adding the following header to the top of the tutorial documentation page:
Without getting too hung up on the phrasing, the key points I would like to highlight are:
that we are aware of the state of the tutorials
that Qiskit Nature is more featureful than the tutorials page might lead to suggest
that we explicitly encourage browsing the code either via the API reference or the code directly
that we encourage users to contribute tutorials (or How-Tos) to help improve and/or expand the available guides
Summary
The tutorials of Qiskit Nature have long been "subpar" and do not cover the full breadth of its capabilities. I think that we need to make our users more aware of that fact or (at least) acknowledge that we are aware of this ourselves in some form or another.
In this PR, I am putting forward a proposal to take care of this. Basically, I am adding the following header to the top of the tutorial documentation page:
Without getting too hung up on the phrasing, the key points I would like to highlight are:
Details and comments