documentation
documentation copied to clipboard
The documentation content home for https://docs.quantum-computing.ibm.com.
### URL, if applicable _No response_ ### Describe the new content you are requesting. Even though we have a [page](https://docs.quantum.ibm.com/guides/error-mitigation-and-suppression-techniques) describing the different error suppression / mitigation methods, not all...
We frequently use the style "`MyClass`s" to refer to multiple objects belong to `MyClass`. It is much more clear to instead say ~"`MyClass` objects"~ "`MyClass` instances". That's better for translation,...
The Compute resources details screens in the UI are being updated. Update the screenshot of the UI [in this page](https://docs.quantum.ibm.com/guides/qpu-information), and verify that other screenshots aren't affected
Today's scheduled test of notebooks that submit jobs failed. Please [check the logs](https://github.com/Qiskit/documentation/actions/runs/11120282996/). > [!NOTE] > This issue was created by a GitHub action.
It's important that the API docs code blocks do not break with code changes. We have too many docs to manually check that there are not issues, so we should...
There will soon be a flag added to Compute resources indicating if a particular QPU supports pulse jobs. Add a clarifying note to the pulse-schedules file pointing users to the...
This PR fixes the code in `serverless-manage-resources.ipynb` and adds tests to check it runs correctly. Link to preview: https://qiskit.github.io/documentation/pr-1960/guides/serverless-manage-resources
We skip all of the notebooks by setting `notebooks_exclude` in `notebook-testing.toml`. Should we test any of these? Update: sync with David, Iskander, and Sanket about what they think is reasonable....
It's currrently possible to merge on red. This is particularly dangerous because the button to "merge when ready" will merge even if "API Checks" and "Execute Notebooks" are red. This...
Implement the design from https://www.figma.com/design/sNXucK1uMaZ8XXyLTZrdrs/IBM-Quantum-Documentation?node-id=7174-39884&t=GIeSutsuCJkUNVjg-1 Because the component is not in the footer, it should probably be a component like ``. The other design I was considering is putting metadata...