deploy documentation in qiskit.org/ecosystem

[1ucian0]

Similar to Qiskit/qiskit-aer#1748, see Qiskit/qiskit.org#3038 for more context

Summary

The Qiskit Ecosystem lives in qiskit.org/ecosystem and new place for qiskit related projects that are not technically Qiskit. This PR adds that destination for documentation deployment.

Details and comments

For now, a copy of the same docs in ecosystem would allow to have both q.o/documentation and q.o/ecosystem for testing that everything is fine. Once that's done, the CDN will redirects to the new location and the deploy to q.o/documentation can be removed.

[coveralls]

Pull Request Test Coverage Report for Build 4507091850

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 50.077%

---

Totals
Change from base Build 4378114609:	0.0%
Covered Lines:	2942
Relevant Lines:	5875

---

💛 - Coveralls

[jyu00]

@1ucian0 https://qiskit.org/ecosystem/ is VERY crowded. Is there a way to ensure qiskit-ibm-runtime and qiskit-ibm-provider get to the top of the page (right now I see qiskit-rigetti as the first one)? Maybe the cards can be sorted by number of downloads?

[1ucian0]

(right now I see qiskit-rigetti as the first one)?

It's random order. It changes weekly.

Maybe the cards can be sorted by number of downloads?

We currently dont have the download information in ecosystem. However, it is an interesting feature. Qiskit/qiskit.org#3045

[jyu00]

@1ucian0 Another question, will there be something saying "this page has been moved" with auto-redirect, so that users don't wake up one day and not know where to find the docs?

[1ucian0]

Yes. The next step in the plan is to set redirects in the CDN. That will create 301 Moved Permanently redirects to the new places. Something like:

[/^qiskit\.org\/documentation\/partners\/qiskit_ibm_provider\/(.*), 'https://qiskit.org/ecosystem/ibm-provider/$1']