🚚 Prepare move to MQT organization (#156)

## Description

This PR prepares the move to the MQT organization.

- Streamline the README.
- Streamline the documentation. Remove work-in-progress files.
Documentation will be added with #103.
- Slightly off topic, but test GitHub Pages build in PRs.

## Checklist:

- [x] The pull request only contains commits that are focused and
relevant to this change.
- [x] ~I have added appropriate tests that cover the new/changed
functionality.~
- [x] ~I have updated the documentation to reflect these changes.~
- [x] The changes follow the project's style guidelines and introduce no
new warnings.
- [x] The changes are fully tested and pass the CI checks.
- [x] I have reviewed my own code changes.

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Author: denialhaag

.github/contributing.md renamed to .github/CONTRIBUTING.md

@@ -5,24 +5,24 @@ We value contributions from people with all levels of experience.
 In particular if this is your first pull request not everything has to be perfect.
 We will guide you through the process.
 
-We use GitHub to [host code](https://github.com/cda-tum/mqt-naviz), to [track issues and feature requests](https://github.com/cda-tum/mqt-naviz/issues), as well as accept [pull requests](https://github.com/cda-tum/mqt-naviz/pulls).
+We use GitHub to [host code](https://github.com/munich-quantum-toolkit/naviz), to [track issues and feature requests](https://github.com/munich-quantum-toolkit/naviz/issues), as well as accept [pull requests](https://github.com/munich-quantum-toolkit/naviz/pulls).
 See <https://docs.github.com/en/get-started/quickstart> for a general introduction to working with GitHub and contributing to projects.
 
 ## Types of Contributions
 
 You can contribute in several ways:
 
 - 🐛 Report Bugs
-  : Report bugs at <https://github.com/cda-tum/mqt-naviz/issues> using the _🐛 Bug report_ issue template. Please make sure to fill out all relevant information in the respective issue form.
+  : Report bugs at <https://github.com/munich-quantum-toolkit/naviz/issues> using the _🐛 Bug report_ issue template. Please make sure to fill out all relevant information in the respective issue form.
 
 - 🐛 Fix Bugs
-  : Look through the [GitHub Issues](https://github.com/cda-tum/mqt-naviz/issues) for bugs. Anything tagged with "bug" is open to whoever wants to try and fix it.
+  : Look through the [GitHub Issues](https://github.com/munich-quantum-toolkit/naviz/issues) for bugs. Anything tagged with "bug" is open to whoever wants to try and fix it.
 
 - ✨ Propose New Features
-  : Propose new features at <https://github.com/cda-tum/mqt-naviz/issues> using the _✨ Feature request_ issue template. Please make sure to fill out all relevant information in the respective issue form.
+  : Propose new features at <https://github.com/munich-quantum-toolkit/naviz/issues> using the _✨ Feature request_ issue template. Please make sure to fill out all relevant information in the respective issue form.
 
 - ✨ Implement New Features
-  : Look through the [GitHub Issues](https://github.com/cda-tum/mqt-naviz/issues) for features. Anything tagged with "feature" or "enhancement" is open to whoever wants to implement it. We highly appreciate external contributions to the project.
+  : Look through the [GitHub Issues](https://github.com/munich-quantum-toolkit/naviz/issues) for features. Anything tagged with "feature" or "enhancement" is open to whoever wants to implement it. We highly appreciate external contributions to the project.
 
 - 📝 Write Documentation
   : MQT NAViz could always use some more documentation, and we appreciate any help with that.

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -8,8 +8,8 @@ body:
         **Thanks for taking the time to report an issue!**
 
         ⚠ Before submitting:
-        1. Search [existing issues](https://github.com/cda-tum/mqt-naviz/search?q=is%3Aissue&type=issues) to avoid duplicates
-        2. For questions or discussions, please use our [discussions forum](https://github.com/cda-tum/mqt-naviz/discussions)
+        1. Search [existing issues](https://github.com/munich-quantum-toolkit/naviz/search?q=is%3Aissue&type=issues) to avoid duplicates
+        2. For questions or discussions, please use our [discussions forum](https://github.com/munich-quantum-toolkit/naviz/discussions)
   - type: textarea
     attributes:
       label: System Information

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -8,7 +8,7 @@ body:
         **Thanks for helping improve this project by suggesting a feature!**
 
         ⚠ Before submitting:
-        - Search [existing feature requests](https://github.com/cda-tum/mqt-naviz/search?q=is%3Aissue&type=issues) to avoid duplicates
+        - Search [existing feature requests](https://github.com/munich-quantum-toolkit/naviz/search?q=is%3Aissue&type=issues) to avoid duplicates
         - One feature per issue helps us track and implement ideas effectively
 
   - type: textarea

.github/release.yaml

@@ -1,11 +1,11 @@
 # Support
 
-If you are stuck with a problem using MQT NAViz or have questions, please get in touch at our [Issues](https://github.com/cda-tum/mqt-naviz/issues) or [Discussions](https://github.com/cda-tum/mqt-naviz/discussions). We'd love to help.
+If you are stuck with a problem using MQT NAViz or have questions, please get in touch at our [Issues](https://github.com/munich-quantum-toolkit/naviz/issues) or [Discussions](https://github.com/munich-quantum-toolkit/naviz/discussions). We'd love to help.
 
 You can save time by following this procedure when reporting a problem:
 
 - Do try to solve the problem on your own first.
-- Search through past [Issues](https://github.com/cda-tum/mqt-naviz/issues) and [Discussions](https://github.com/cda-tum/mqt-naviz/discussions) to see if someone else already had the same problem.
+- Search through past [Issues](https://github.com/munich-quantum-toolkit/naviz/issues) and [Discussions](https://github.com/munich-quantum-toolkit/naviz/discussions) to see if someone else already had the same problem.
 - Before filing a bug report, try to create a minimal working example (MWE) that reproduces the problem. It is much easier to identify the cause for the problem if a handful of lines suffice to show that something is not working.
 
 You can also always reach us at [[email protected]](mailto:[email protected]).

.github/support.md

@@ -11,8 +11,11 @@ on:
   push:
     branches:
       - main
-    tags:
-      - "v*" # Rebuild when a full version is released
+  release:
+    types: [published]
+  pull_request:
+  merge_group:
+  workflow_dispatch:
 
 # Cancel any old builds when starting a new build
 concurrency:
@@ -52,6 +55,7 @@ jobs:
           path: ./gui/dist
 
   deploy:
+    if: github.ref == 'refs/heads/main'
     environment:
       name: github-pages
       url: ${{ steps.deployment.outputs.page_url }}

.github/workflows/github-pages.yaml

@@ -2,7 +2,9 @@ version: 2
 
 formats:
   - htmlzip
-  # - pdf
+
+sphinx:
+  configuration: docs/conf.py
 
 build:
   os: ubuntu-24.04
@@ -39,11 +41,3 @@ build:
         - uv run --frozen --no-dev --no-build-isolation-package mqt-naviz -m sphinx -T -b dirhtml -d docs/_build/doctrees -D language=en docs docs/_build/dirhtml
         - mkdir -p $READTHEDOCS_OUTPUT/htmlzip
         - zip -r $READTHEDOCS_OUTPUT/htmlzip/html.zip docs/_build/dirhtml/*
-      # pdf:
-      #   - uv run --frozen --no-dev --no-build-isolation-package mqt-naviz -m sphinx -T -b latex -d docs/_build/doctrees -D language=en docs docs/_build/latex
-      #   - cd docs/_build/latex && latexmk -pdf -f -dvi- -ps- -interaction=nonstopmode -jobname=$READTHEDOCS_PROJECT
-      #   - mkdir -p $READTHEDOCS_OUTPUT/pdf
-      #   - cp docs/_build/latex/$READTHEDOCS_PROJECT.pdf $READTHEDOCS_OUTPUT/pdf/$READTHEDOCS_PROJECT.pdf
-
-sphinx:
-  configuration: docs/conf.py

.readthedocs.yml

@@ -14,7 +14,7 @@ resolver = "2"
 
 [workspace.package]
 license = "LGPL-3.0-or-later WITH LGPL-3.0-linking-exception"
-repository = "https://github.com/cda-tum/mqt-naviz"
+repository = "https://github.com/munich-quantum-toolkit/naviz"
 
 [workspace.dependencies]
 naviz-animator = {path = "animator", version = "0.4.1"}

Cargo.toml

@@ -1,9 +1,3 @@
-<!-- [![PyPI](https://img.shields.io/pypi/v/mqt.naviz?logo=pypi&style=flat-square)](https://pypi.org/project/mqt.naviz/) -->
-<!-- ![OS](https://img.shields.io/badge/os-linux%20%7C%20macos%20%7C%20windows-blue?style=flat-square) -->
-<!-- [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](https://opensource.org/licenses/MIT) -->
-<!-- [![CI](https://img.shields.io/github/actions/workflow/status/cda-tum/mqt-naviz/ci.yml?branch=main&style=flat-square&logo=github&label=ci)](https://github.com/cda-tum/mqt-naviz/actions/workflows/ci.yml) -->
-<!-- [![CD](https://img.shields.io/github/actions/workflow/status/cda-tum/mqt-naviz/cd.yml?style=flat-square&logo=github&label=cd)](https://github.com/cda-tum/mqt-naviz/actions/workflows/cd.yml) -->
-
 [![Documentation](https://img.shields.io/readthedocs/mqt-naviz?logo=readthedocs&style=flat-square)](https://mqt.readthedocs.io/projects/naviz)
 
 <p align="center">
@@ -35,7 +29,7 @@ It is developed as part of the [_Munich Quantum Toolkit (MQT)_](https://mqt.read
 - Support for different input formats
 - Fully customizable visualization style and clean predefined styles
 
-If you have any questions, feel free to create a [discussion](https://github.com/cda-tum/mqt-naviz/discussions) or an [issue](https://github.com/cda-tum/mqt-naviz/issues) on [GitHub](https://github.com/cda-tum/mqt-naviz).
+If you have any questions, feel free to create a [discussion](https://github.com/munich-quantum-toolkit/naviz/discussions) or an [issue](https://github.com/munich-quantum-toolkit/naviz/issues) on [GitHub](https://github.com/munich-quantum-toolkit/naviz).
 
 ## Contributors and Supporters
 
@@ -52,11 +46,46 @@ Among others, it is part of the [Munich Quantum Software Stack (MQSS)](https://w
 Thank you to all the contributors who have helped make MQT NAViz a reality!
 
 <p align="center">
-<a href="https://github.com/cda-tum/mqt-naviz/graphs/contributors">
-  <img src="https://contrib.rocks/image?repo=cda-tum/mqt-naviz" />
+<a href="https://github.com/munich-quantum-toolkit/naviz/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=munich-quantum-toolkit/naviz" />
 </a>
 </p>
 
+The MQT will remain free, open-source, and permissively licensed—now and in the future.
+We are firmly committed to keeping it open and actively maintained for the quantum computing community.
+
+To support this endeavor, please consider:
+
+- Starring and sharing our repositories: https://github.com/munich-quantum-toolkit
+- Contributing code, documentation, tests, or examples via issues and pull requests
+- Citing the MQT in your publications (see [Cite This](#cite-this))
+- Using the MQT in research and teaching, and sharing feedback and use cases
+- Sponsoring us on GitHub: https://github.com/sponsors/munich-quantum-toolkit
+
+<p align="center">
+  <a href="https://github.com/sponsors/munich-quantum-toolkit">
+  <img width=20% src="https://img.shields.io/badge/Sponsor-white?style=for-the-badge&logo=githubsponsors&labelColor=black&color=blue" alt="Sponsor the MQT" />
+  </a>
+</p>
+
+## Cite This
+
+When discussing the overall MQT project or its ecosystem, please cite the MQT Handbook:
+
+```bibtex
+@inproceedings{mqt,
+  title        = {The {{MQT}} Handbook: {{A}} Summary of Design Automation Tools and Software for Quantum Computing},
+  shorttitle   = {{The MQT Handbook}},
+  author       = {Will, Robert and Berent, Lucas and Forster, Tobias and Kunasaikaran, Jagatheesan and Mato, Kevin and Peham, Tom and Quetschlich, Nils and Rovara, Damian and Sander, Aaron and Schmid, Ludwig and Schoenberger, Daniel and Stade, Yannick and Burgholzer, Lukas},
+  year         = 2024,
+  booktitle    = {IEEE International Conference on Quantum Software (QSW)},
+  doi          = {10.1109/QSW62656.2024.00013},
+  eprint       = {2405.17543},
+  eprinttype   = {arxiv},
+  addendum     = {A live version of this document is available at \url{https://mqt.readthedocs.io}}
+}
+```
+
 ---
 
 ## Acknowledgements