Content audit for qiskit documentation

[y4izus]

Content on documentation comes from different repos and in different ways, so we need to know where those files live:

• Remove deepcopy usage in dag_to_circuit qiskit#1431

In addition, the idea is to organize the documentation following the structure proposed by divio. Right now we have 3 types of documentation: API References, getting started files and tutorials. First one is attached to the code but the second and third ones are on different folders. We would like to know if those tutorials and getting started files fits the tutorials definition given on divio or if they belongs to any of the other categories: API References, how-to guides or explanations.

A proposal is to come up with a summary with this structure (I've added an example):

Project	Tutorial	Source File	Doc type
Qiskit Nature	Electronic Structure	Link on qiskit-nature repo	Tutorial

Where:

• Project can be:
  • Qiskit core
  • Qiskit machine learning
  • Qiskit nature
  • Qiskit finance
  • Qiskit optimization
  • Qiskit experiments
  • Qiskit dynamics
  • Qiskit metal
  • Qiskit partners
• Tutorial is the name of the tutorial and point to the page under qiskit.org/documentation. If the tutorial is under a category, you can add it too
• Source file is the name to the repo where the tutorial lives and point to its code file
• Doc Type can be:
  • API Reference
  • Tutorial
  • How-to guide
  • Explanation

There is a lot of content to review, so I'm gonna split this task in smaller ones

• As a content creator I would like to have an example for each doc type #223. Documentation built through the qiskit metapackage
• Add support to qobj_to_circuits for qobj without qasm qiskit#1423
• crash when set initial_state with complex vector for simulator qiskit#1424
• setting max qubit in unitary qiskit#1425
• Wire fragment bug in mapper qiskit#1426
• Use integers in properties.gates.qubits qiskit#1427
• Make to_dict and from_dict more discoverable, adjust converter tests qiskit#1428
• Circuits qiskit#1429
• check backend configuration in compile qiskit#1430

[1ucian0]

I moved these issue to qiskit/qiskit_sphinx_theme as this content audit might be something under the Doc Guide. This should have a lower priority that the initial one. Once this epic gets ready to be worked on, let's reopen/create the task issues.