qiskit-metapackage
qiskit-metapackage copied to clipboard
Qiskit
Qiskit is an open-source SDK for working with quantum computers at the level of circuits, algorithms, and application modules.
Part of https://github.com/Qiskit/qiskit/issues/1523
Part of https://github.com/Qiskit/qiskit/issues/1523
Part of https://github.com/Qiskit/qiskit/issues/1523
Using our [tutorial's checklist](https://ibm.ent.box.com/notes/967973419693), make sure that our our advanced circuits tutorials has the quality we want, and if not, improve them: - [ ] https://github.com/Qiskit/qiskit/issues/1524 - [ ] https://github.com/Qiskit/qiskit/issues/1525...
We are trying to follow the same content structure for all qiskit repos that has its documentation on the [qiskit documentation page](https://qiskit.org/documentation). We started with the [runtime documentation](https://qiskit.org/documentation/partners/qiskit_ibm_runtime/). As you...
With the [removal of Aer from the metapackage](https://github.com/Qiskit/qiskit-aer/pull/1526), a documentation page for its own is needed. Once Aer is removed from the metapackage, the module will be at the same...
The documentation page is built with Sphinx pulling the content from different repositories. This issue is intended to identify from which repos and what info we are getting
It seems like all the modules use `apidocs/` (eg https://qiskit.org/documentation/nature/apidocs/qiskit_nature.html) while the metapackage refers to `apidoc/` (eg https://qiskit.org/documentation/apidoc/terra.html). It would be nice to unify the nomenclature there.