remove dgl from docs (#116)

This removes DGL from the docs 
Resolves #111 
Resolves #110
Resolves #91

Authors:
  - Don Acosta (https://github.com/acostadon)

Approvers:
  - Brad Rees (https://github.com/BradReesWork)

URL: #116

Author: acostadon

docs/cugraph-docs/source/_static/cugraph-pyg-stack.png

@@ -22,7 +22,6 @@ Graph Neural Networks API Documentation
     :maxdepth: 3
     :caption: Graph Neural Networks API Documentation
 
-    cugraph-dgl/cugraph_dgl.rst
     cugraph-pyg/cugraph_pyg.rst
     .. wholegraph/index.rst
 

docs/cugraph-docs/source/api_docs/cugraph-dgl/cugraph_dgl.old

@@ -77,7 +77,7 @@
 
 # General information about the project.
 project = 'cugraph-docs'
-copyright = '2024, NVIDIA Corporation'
+copyright = '2024-2025, NVIDIA Corporation'
 author = 'NVIDIA Corporation'
 
 # The version info for the project you're documenting, acts as replacement for
@@ -102,6 +102,9 @@
 # This patterns also effect to html_static_path and html_extra_path
 exclude_patterns = []
 
+suppress_warnings = ['duplicate_declaration.cpp']
+
+
 # The name of the Pygments (syntax highlighting) style to use.
 pygments_style = 'sphinx'
 

docs/cugraph-docs/source/api_docs/cugraph-dgl/cugraph_dgl.rst

@@ -5,7 +5,7 @@ There are multiple ways to be involved and contribute to the cuGraph community,
 
 * [File an Issue](https://github.com/rapidsai/docs/issues/new)
 * [Implement a New Feature](https://docs.rapids.ai/contributing/code/#your-first-issue)
-* [Work on an Existing Issue](#F)
+* [Work on an Existing Issue](https://github.com/rapidsai/cugraph/issues)
 
 If you are ready to contribute, jump right to the [Contribute Code](https://docs.rapids.ai/contributing/issues/) section.
 
@@ -69,17 +69,15 @@ If you need more context on a particular issue, please ask.
 ## So you want to contribute code
 
 **TL;DR General Development Process**
-1. Read the documentation on [building from source](https://docs.rapids.ai/api/cugraph/nightly/installation/source_build/) to learn how to setup, and validate, the development environment
-2. Read the RAPIDS [Code of Conduct](https://docs.rapids.ai/resources/conduct/)
-3. Find or submit an issue to work on (include a comment that you are working issue)
-4. Fork the cuGraph [repo](#fork) and Code (make sure to add unit tests)!
+1. Read the project's README to learn how to setup the development environment
+2. Find an issue to work on. The best way is to look for the <span class="label" style="background: #7057ff; color: #ffffff; text-transform: none">good first issue</span> or <span class="label" style="background: #008672; color: #ffffff; text-transform: none">help wanted</span> labels
+3. Comment on the issue saying you are going to work on it
+4. Code! Make sure to update unit tests!
 5. All RAPIDS projects are released under the Apache-2.0 license, so also make sure all source files that support comments include a copyright and the Apache-2.0 license text.
-6. When done, and code passes local CI, create your pull request (PR)
-   1. Ensure the code matches the [style guide](https://docs.rapids.ai/resources/style/)
-7. Verify that cuGraph CI passes all [status checks](https://help.github.com/articles/about-status-checks/). Fix if needed
+6. When done, [create your pull request]({% link contributing/prs.md %})
+7. Verify that CI passes all [status checks](https://help.github.com/articles/about-status-checks/). Fix if needed
 8. Wait for other developers to review your code and update code as needed
-9. PR will require the proper [tags](https://docs.rapids.ai/resources/label-checker/) be added by someone with repository permission.
-10. Once reviewed and approved, a RAPIDS developer will merge your pull request
+9. Once reviewed and approved, a RAPIDS developer will merge your pull request
 
 Remember, if you are unsure about anything, don't hesitate to comment on issues
 and ask for clarifications!
@@ -115,7 +113,7 @@ cuGraph only allows contribution to the current branch and not main or a future
    1. commit your code
     ```git push```
 6. From the GitHub web page, open a Pull Request
-   1. follow the Pull Request [tagging policy](./PRTAGS.md)
+   1. follow the Pull Request in the repository: https://github.com/rapidsai/```<REPO NAME>```/pulls
 
 ### Development Environment
 

docs/cugraph-docs/source/api_docs/index.rst

@@ -84,8 +84,6 @@ and we try to follow his rules: "No raw loops. No raw pointers. No raw synchroni
  * Prefer algorithms from STL and Thrust to raw loops.
  * Prefer cugraph and RMM to raw pointers and raw memory allocation.
 
-Documentation is discussed in the [Documentation Guide](TODO).
-
 ### Includes
 
 The following guidelines apply to organizing `#include` lines.

docs/cugraph-docs/source/basics/index.md

@@ -2,14 +2,28 @@
 Graph Neural Network Support
 ============================
 
+**cuGraph-DGL has been removed from cuGraph GNN as of release 25.06.** We recommend migrating to 
+cuGraph-PyG, which offers the same functionality along with additional features like support for heterogeneous sampling and a unified API. 
+The cuGraph team is not planning any further work in the DGL ecosystem going forward.
+
+----
+
+The cuGraph GNN stack
+
+.. image:: ../../_static/cugraph-pyg-stack.png
+   :alt: The cuGraph-
+   :width: 400px
+   :align: center
+
+----
+
 Here is a talk that explains `Training GNNs at Internet Scale using cuGraph and WholeGraph <https://www.youtube.com/watch?v=rS-bcWm3jQo&t=2762s>`_
 
 
 .. toctree::
    :maxdepth: 2
 
    PyG_support.md
-   DGL_support.md
    wholegraph_support.md
 
 Blogs to explain how RAPIDS cuGraph supports GNN'S