[6.0.x] Refs #35859 -- Mentioned django-tasks and external resources on docs/topics/tasks.txt.

Backport of a328c355d9625ecdc8f16b249daebba3c0ac2882 from main.

1 files changed, 9 insertions, 2 deletions

diff --git a/docs/topics/tasks.txt b/docs/topics/tasks.txt
index 06e83af0bc..d3bc54f6b4 100644
--- a/docs/topics/tasks.txt
+++ b/docs/topics/tasks.txt
@@ -4,6 +4,8 @@ Django's Tasks framework
 
 .. versionadded:: 6.0
 
+    For older Django versions, the :pypi:`django-tasks` backport is available.
+
 For a web application, there's often more than just turning HTTP requests into
 HTTP responses. For some functionality, it may be beneficial to run code
 outside the request-response cycle.
@@ -113,8 +115,13 @@ Third-party backends
 
 As mentioned at the beginning of this section, Django includes backends
 suitable for development and testing only. Production systems should rely on
-backends that supply a worker process and durable queue implementation. To use
-an external Task backend with Django, use the Python import path as the
+backends that supply a worker process and a durable queue implementation.
+Available third-party backends are listed on the `Community Ecosystem page
+<https://www.djangoproject.com/community/ecosystem/#tasks>`__ and the `Tasks
+framework grid from Django Packages
+<https://djangopackages.org/grids/g/task-framework/>`__.
+
+To use an external Task backend with Django, use the Python import path as the
 :setting:`BACKEND <TASKS-BACKEND>` of the :setting:`TASKS` setting, like so::
 
     TASKS = {