From f1b699a55ac127dc3526381976971e14c9f39b14 Mon Sep 17 00:00:00 2001
From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Date: Fri, 28 Nov 2025 14:57:06 +0100
Subject: [PATCH 1/2] Updated CoC as WG rather than committee and linked to
 team page.

---
 djangoproject/templates/conduct/base.html     |  2 +-
 djangoproject/templates/conduct/changes.html  |  2 +-
 .../templates/conduct/enforcement.html        | 83 ++++++++++---------
 .../templates/conduct/reporting.html          | 21 ++---
 4 files changed, 55 insertions(+), 53 deletions(-)

diff --git a/djangoproject/templates/conduct/base.html b/djangoproject/templates/conduct/base.html
index b7eaf1c390..19f980eba1 100644
--- a/djangoproject/templates/conduct/base.html
+++ b/djangoproject/templates/conduct/base.html
@@ -11,7 +11,7 @@ <h2 id="aside-header">{% translate "Django Community Code of Conduct" %}</h2>
 
     <ul class="list-links">
       <li><a href="{% url 'code_of_conduct' %}">{% translate "Code of Conduct" %}</a></li>
-      <li><a href="/foundation/committees/#conduct">{% translate "Committee" %}</a></li>
+      <li><a href="{% url 'members:teams' %}#code-of-conduct-team">{% translate "Code of Conduct working group" %}</a></li>
       <li><a href="{% url 'conduct_faq' %}">{% translate "Frequently Asked Questions" %}</a></li>
       <li><a href="{% url 'conduct_reporting' %}">{% translate "Reporting Guide" %}</a></li>
       <li><a href="{% url 'conduct_enforcement' %}">{% translate "Enforcement Manual" %}</a></li>
diff --git a/djangoproject/templates/conduct/changes.html b/djangoproject/templates/conduct/changes.html
index a954aa8147..024870aa6b 100644
--- a/djangoproject/templates/conduct/changes.html
+++ b/djangoproject/templates/conduct/changes.html
@@ -17,7 +17,7 @@ <h2>{% translate "Change control process" %}</h2>
       associated documents the same way we track changes to code. All changes will
       be proposed via a pull request to the
       <a href="https://github.com/django/djangoproject.com">djangoproject.com repository
-        on GitHub</a>. Changes will be reviewed by the conduct committee first, and then
+        on GitHub</a>. Changes will be reviewed by the conduct working group first, and then
       sent to the DSF and the Django community for comment.
       We'll hold a comment period of at least one week, then the DSF board will vote on
       the change. Approved changes will be merged, published, and noted below.{% endblocktranslate %}</p>
diff --git a/djangoproject/templates/conduct/enforcement.html b/djangoproject/templates/conduct/enforcement.html
index 414d1b39a9..5605d92885 100644
--- a/djangoproject/templates/conduct/enforcement.html
+++ b/djangoproject/templates/conduct/enforcement.html
@@ -4,7 +4,7 @@
 {% block title %}{% translate "Django Code of Conduct - Enforcement Manual" %}{% endblock %}
 
 {% block og_title %}{% translate "Django Code of Conduct - Enforcement Manual" %}{% endblock %}
-{% block og_description %}{% translate "This is the enforcement manual followed by Django's Code of Conduct Committee" %}{% endblock %}
+{% block og_description %}{% translate "This is the enforcement manual followed by Django's Code of Conduct working group" %}{% endblock %}
 
 {% block content %}
   <h1>{% translate "Django Code of Conduct - Enforcement Manual" %}</h1>
@@ -12,34 +12,35 @@ <h1>{% translate "Django Code of Conduct - Enforcement Manual" %}</h1>
   <h2 class="deck">
     {% blocktranslate trimmed %}
       This is the enforcement manual followed by Django's Code of
-      Conduct Committee. It's used when we respond to an issue to make sure we're
+      Conduct working group. It's used when we respond to an issue to make sure we're
       consistent and fair. It should be considered an internal document, but we're
       publishing it publicly in the interests of transparency.
     {% endblocktranslate %}</h2>
 
-  <h3>{% translate "The Code of Conduct Committee" %}</h3>
+  <h3>{% translate "The Code of Conduct Working Group" %}</h3>
 
   <p>
+    {% url 'members:teams' as teams_url %}
     {% blocktranslate trimmed %}
-      All responses to reports of conduct violations will be managed by a
-      <a href="/foundation/committees/">Code of Conduct Committee</a> ("the committee").
+      All responses to reports of conduct violations will be managed by the
+      <a href="{{ teams_url }}#code-of-conduct-team">Code of Conduct working group</a>.
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
       The Django Software Foundation's Board of Directors ("the board") will establish
-      this committee, comprised of at least three members. One member will be
-      designated chair of the committee and will be responsible for all reports back to
+      this working group, comprised of at least three members. One member will be
+      designated chair of the working group and will be responsible for all reports back to
       the board. The board will review membership on a regular basis.
     {% endblocktranslate %}</p>
 
-  <h3>{% translate "How the committee will respond to reports" %}</h3>
+  <h3>{% translate "How the working group will respond to reports" %}</h3>
 
   <p>
     {% blocktranslate trimmed %}
-      When a report is sent to the committee they will immediately reply to the
+      When a report is sent to the working group they will immediately reply to the
       report to confirm receipt. This reply must be sent within 24 hours, and the
-      committee should strive to respond much quicker than that.
+      working group should strive to respond much quicker than that.
     {% endblocktranslate %}</p>
 
   {% url 'conduct_reporting' as conduct_reporting %}
@@ -47,12 +48,12 @@ <h3>{% translate "How the committee will respond to reports" %}</h3>
     {% blocktranslate trimmed %}
       See the <a href="{{ conduct_reporting }}">reporting guidelines</a> for details of
       what reports should contain. If a report doesn't contain enough information, the
-      committee will obtain all relevant data before acting. The committee is
+      working group will obtain all relevant data before acting. The working group is
       empowered to act on the DSF's behalf in contacting any individuals involved to
       get a more complete account of events.
     {% endblocktranslate %}</p>
 
-  <p>{% translate "The committee will then review the incident and determine, to the best of their ability:" %}
+  <p>{% translate "The working group will then review the incident and determine, to the best of their ability:" %}
     <ul>
       <li>{% translate "what happened" %}</li>
       <li>{% translate "whether this event constitutes a code of conduct violation" %}</li>
@@ -64,14 +65,14 @@ <h3>{% translate "How the committee will respond to reports" %}</h3>
   <p>
     {% blocktranslate trimmed %}
       This information will be collected in writing, and whenever possible the
-      committee's deliberations will be recorded and retained (i.e. chat transcripts, email
+      working group's deliberations will be recorded and retained (i.e. chat transcripts, email
       discussions, recorded voice conversations, etc).
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      The committee should aim to have a resolution agreed upon within one week.
-      In the event that a resolution can't be determined in that time, the committee will
+      The working group should aim to have a resolution agreed upon within one week.
+      In the event that a resolution can't be determined in that time, the working group will
       respond to the reporter(s) with an update and projected timeline for resolution.
     {% endblocktranslate %}</p>
 
@@ -80,30 +81,30 @@ <h3>{% translate "Acting Unilaterally" %}</h3>
   <p>
     {% blocktranslate trimmed %}
       If the act is ongoing (such as someone engaging in harassment on the forum), or involves
-      a threat to anyone's safety (e.g. threats of violence), any committee member
+      a threat to anyone's safety (e.g. threats of violence), any working group member
       may act immediately (before reaching consensus) to end the situation. In ongoing
       situations, any member may at their discretion employ any of the tools available
-      to the committee, including bans and blocks.
+      to the working group, including bans and blocks.
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      If the incident involves physical danger, any member of the committee may --
+      If the incident involves physical danger, any member of the working group may --
       and should -- act unilaterally to protect safety. This can include contacting
       law enforcement (or other local personnel) and speaking on behalf of the DSF.
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      In situations where an individual committee member acts unilaterally, they must
-      report their actions to the committee for review within 24 hours.{% endblocktranslate %}</p>
+      In situations where an individual working group member acts unilaterally, they must
+      report their actions to the working group for review within 24 hours.{% endblocktranslate %}</p>
 
   <h3>{% translate "Resolutions" %}</h3>
 
   <p>
     {% blocktranslate trimmed %}
-      The committee must agree on a resolution by consensus. If the committee cannot
-      reach consensus and deadlocks for over a week, the committee will turn the matter
+      The working group must agree on a resolution by consensus. If the working group cannot
+      reach consensus and deadlocks for over a week, the working group will turn the matter
       over to the board for resolution.{% endblocktranslate %}</p>
 
   <p>{% translate "Possible responses may include:" %}
@@ -111,55 +112,55 @@ <h3>{% translate "Resolutions" %}</h3>
       <li>{% translate "Taking no further action (if we determine no violation occurred)." %}</li>
       <li>
         {% blocktranslate trimmed %}
-          A private reprimand from the committee to the individual(s) involved.
-          In this case, a committee member will deliver that reprimand to the individual(s)
-          over email, cc'ing the committee.{% endblocktranslate %}</li>
+          A private reprimand from the working group to the individual(s) involved.
+          In this case, a working group member will deliver that reprimand to the individual(s)
+          over email, cc'ing the working group.{% endblocktranslate %}</li>
       <li>
         {% blocktranslate trimmed %}
-          A public reprimand. In this case, a committee member will deliver that reprimand
+          A public reprimand. In this case, a working group member will deliver that reprimand
           in the same venue that the violation occurred (i.e. in the forum for a forum violation;
-          email for an email violation, etc.). The committee may choose to publish this message
+          email for an email violation, etc.). The working group may choose to publish this message
           elsewhere for posterity.{% endblocktranslate %}</li>
       <li>
         {% blocktranslate trimmed %}
           An imposed vacation (i.e. asking someone to "take a week off" from the forum).
-          A committee member will communicate this "vacation" to the individual(s).
+          A working group member will communicate this "vacation" to the individual(s).
           They'll be asked to take this vacation voluntarily, but if they don't agree then
           a temporary ban may be imposed to enforce this vacation.{% endblocktranslate %}</li>
       <li>
         {% blocktranslate trimmed %}
           A permanent or temporary ban from some or all Django spaces (the forum,
-          etc.). The committee will maintain records of all such bans so that they may be
+          etc.). The working group will maintain records of all such bans so that they may be
           reviewed in the future, extended to new Django fora, or otherwise maintained.
         {% endblocktranslate %}</li>
       <li>
         {% blocktranslate trimmed %}
-          A request for a public or private apology. a committee member will deliver this request.
-          The committee may, if it chooses, attach "strings" to this request: for example,
-          the committee may ask a violator to apologize in order to retain his or her membership
+          A request for a public or private apology. a working group member will deliver this request.
+          The working group may, if it chooses, attach "strings" to this request: for example,
+          the working group may ask a violator to apologize in order to retain his or her membership
           on the forum.{% endblocktranslate %}</li>
     </ul>
   </p>
 
   <p>
     {% blocktranslate trimmed %}
-      Once a resolution is agreed upon, but before it is enacted, the committee
+      Once a resolution is agreed upon, but before it is enacted, the working group
       will contact the original reporter and any other affected parties and explain
-      the proposed resolution. The committee will ask if this resolution is
-      acceptable, and must note feedback for the record. However, the committee is
+      the proposed resolution. The working group will ask if this resolution is
+      acceptable, and must note feedback for the record. However, the working group is
       not required to act on this feedback.
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      Finally the committee will make a report for the DSF board. In case the
-      incident or report involves a current member of the board, the committee will
+      Finally the working group will make a report for the DSF board. In case the
+      incident or report involves a current member of the board, the working group will
       provide the report only to the other board members.
     {% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      The committee will never publicly discuss the issue; all public statements
+      The working group will never publicly discuss the issue; all public statements
       will be made by the DSF board.
     {% endblocktranslate %}</p>
 
@@ -167,11 +168,11 @@ <h3>{% translate "Conflicts of Interest" %}</h3>
   {% url 'conduct_reporting' as url%}
   <p>
     {% blocktranslate trimmed %}
-      In the event of any conflict of interest a committee member must immediately
+      In the event of any conflict of interest a working group member must immediately
       notify the other members, and recuse themselves if necessary. If a report concerns
-      a possible violation by a current committee member, this member should be
+      a possible violation by a current working group member, this member should be
       excluded from the response process. For these cases, anyone can make a report
-      directly to any of the committee chairs, as documented in the
+      directly to any of the working group chairs, as documented in the
       <a href="{{ url }}">reporting guidelines</a>.
     {% endblocktranslate %}</p>
 
diff --git a/djangoproject/templates/conduct/reporting.html b/djangoproject/templates/conduct/reporting.html
index 277978481c..b4852a3cbf 100644
--- a/djangoproject/templates/conduct/reporting.html
+++ b/djangoproject/templates/conduct/reporting.html
@@ -103,26 +103,27 @@ <h3>{% translate "What happens after you file a report?" %}</h3>
       Finally, the Working Group will make a report on the situation to the DSF board.
       The board may choose to a public report of the incident.{% endblocktranslate %}</p>
 
-  <h3>{% translate "What if your report concerns a possible violation by a committee member?" %}</h3>
+  <h3>{% translate "What if your report concerns a possible violation by a working group member?" %}</h3>
 
   <p>
     {% blocktranslate trimmed %}
-      If your report concerns a current member of the Code of Conduct committee, you
-      may not feel comfortable sending your report to the committee, as all members will
+      If your report concerns a current member of the Code of Conduct working group, you
+      may not feel comfortable sending your report to the working group, as all members will
       see the report.{% endblocktranslate %}</p>
 
   <p>
+    {% url 'members:teams' as teams_url %}
     {% blocktranslate trimmed %}
       In that case, you can make a report directly to any or all of the current
-      (vice/co) chairs of the Code of Conduct committee. Their e-mail addresses are
-      listed on the <a href="/foundation/committees/">Code of Conduct Committee</a>
-      page. The chairs will follow the usual enforcement process with the other
-      members, but will exclude the member(s) that the report concerns from any
-      discussion or decision making.{% endblocktranslate %}</p>
+      (vice/co) chairs of the Code of Conduct working group. Their e-mail addresses are
+      listed on the <a href="{{ teams_url }}#code-of-conduct-team">Code of
+        Conduct working group</a> page. The chairs will follow the usual enforcement
+      process with the other members, but will exclude the member(s) that the report
+      concerns from any discussion or decision making.{% endblocktranslate %}</p>
 
   <p>
     {% blocktranslate trimmed %}
-      If your report concerns all current (vice/co) chairs of the committee, please
+      If your report concerns all current (vice/co) chairs of the working group, please
       send your report directly to the DSF board at
       <a href="mailto:foundation@djangoproject.com">foundation@djangoproject.com</a>
       instead.{% endblocktranslate %}</p>
@@ -132,7 +133,7 @@ <h3>{% translate "Reconsideration" %}</h3>
   <p>
     {% blocktranslate trimmed %}
       Any of the parties directly involved or affected can request reconsideration
-      of the committee’s decision. To make such a request, contact the DSF Board at
+      of the working group’s decision. To make such a request, contact the DSF Board at
       <a href="mailto:foundation@djangoproject.com">foundation@djangoproject.com</a>
       with your request and motivation and the DSF board will review the case.{% endblocktranslate %}</p>
 

From 53b050dad2651436d2bb08b09e1f89749cd7d362 Mon Sep 17 00:00:00 2001
From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Date: Fri, 28 Nov 2025 15:03:48 +0100
Subject: [PATCH 2/2] Removed relative urls.

---
 .../templates/aggregator/ecosystem.html       |  8 +++---
 djangoproject/templates/aggregator/index.html |  4 +--
 djangoproject/templates/base_community.html   |  8 +++---
 djangoproject/templates/base_foundation.html  | 10 +++----
 djangoproject/templates/base_weblog.html      |  4 +--
 .../templates/fundraising/index.html          | 27 ++++++++++---------
 djangoproject/templates/homepage.html         | 12 ++++-----
 djangoproject/templates/includes/footer.html  |  8 +++---
 .../members/corporate_member_badges.html      |  3 ++-
 .../members/corporatemember_list.html         |  5 ++--
 .../templates/members/team_list.html          |  3 ++-
 .../templates/releases/download.html          |  2 +-
 djangoproject/templates/releases/roadmap.html | 12 ++++-----
 docs/templates/docs/doc.html                  |  2 +-
 members/forms.py                              |  8 +++---
 releases/tests.py                             | 10 ++-----
 16 files changed, 63 insertions(+), 63 deletions(-)

diff --git a/djangoproject/templates/aggregator/ecosystem.html b/djangoproject/templates/aggregator/ecosystem.html
index 91b6296cd7..77c9872353 100644
--- a/djangoproject/templates/aggregator/ecosystem.html
+++ b/djangoproject/templates/aggregator/ecosystem.html
@@ -1,5 +1,5 @@
 {% extends "base_community.html" %}
-{% load i18n %}
+{% load i18n hosts %}
 
 {% block content %}
 
@@ -139,7 +139,7 @@ <h3 id="tutorials">
   <ul>
     <li>
       <a href="https://tutorial.djangogirls.org/">DjangoGirls Tutorial</a>
-      &mdash; A great tutorial you can do in addition to the <a href="/en/dev/intro/tutorial/01/">official tutorial</a>.
+      &mdash; A great tutorial you can do in addition to the <a href="{% url 'document-detail' lang='en' version='stable' url='intro/tutorial/01/' host 'docs' %}">official tutorial</a>.
     </li>
   </ul>
 
@@ -152,10 +152,10 @@ <h3 id="miscellaneous">
       <a href="https://builtwithdjango.com/projects/" rel="nofollow">Django-powered sites</a>
     </li>
     <li>
-      <a href="/community/badges/">Show your support with badges</a>
+      <a href="{% host_url "homepage" host "www" %}community/badges/">Show your support with badges</a>
     </li>
     <li>
-      <a href="/community/logos/">Download official logos</a>
+      <a href="{% host_url "homepage" host "www" %}community/logos/">Download official logos</a>
     </li>
   </ul>
 
diff --git a/djangoproject/templates/aggregator/index.html b/djangoproject/templates/aggregator/index.html
index 461fed46b5..527351e443 100644
--- a/djangoproject/templates/aggregator/index.html
+++ b/djangoproject/templates/aggregator/index.html
@@ -39,7 +39,7 @@ <h3>{% translate "Package Ecosystem" %}</h3>
 
   <h2 class="community-title">{% translate "Get Involved" %}</h2>
   <div class="community-cta-wrapper">
-    <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-bugs" class="community-cta-a">
+    <a href="{% url 'document-detail' lang='en' version='dev' url='internals/contributing/bugs-and-features' host 'docs' %}#reporting-bugs" class="community-cta-a">
       <div class="community-cta">
         <div>
           {% include "svg_logos/bug.html" %}
@@ -47,7 +47,7 @@ <h2 class="community-title">{% translate "Get Involved" %}</h2>
         <h3>{% translate "Report an issue" %}</h3>
       </div>
     </a>
-    <a href="https://docs.djangoproject.com/en/dev/internals/contributing/" class="community-cta-a">
+    <a href="{% url 'document-detail' lang='en' version='dev' url='internals/contributing' host 'docs' %}" class="community-cta-a">
       <div class="community-cta">
         <div>
           {% include "svg_logos/notepad.html" %}
diff --git a/djangoproject/templates/base_community.html b/djangoproject/templates/base_community.html
index fa76161a11..848fad59a0 100644
--- a/djangoproject/templates/base_community.html
+++ b/djangoproject/templates/base_community.html
@@ -1,5 +1,5 @@
 {% extends "base.html" %}
-{% load fundraising_extras i18n %}
+{% load fundraising_extras i18n hosts %}
 
 {% block og_title %}{% translate "Django Community" %}{% endblock %}
 {% block og_description %}{% translate "Building the Django Community. Come join us!" %}{% endblock %}
@@ -45,7 +45,7 @@ <h3>{% translate "Dive In" %}</h3>
     <dl class="list-links">
       <dt><a href="https://code.djangoproject.com/">{% translate "Ticket System" %}</a></dt>
       <dd>{% translate "View and update bug reports" %}</dd>
-      <dt><a href="https://dashboard.djangoproject.com/">{% translate "Development Dashboard" %}</a></dt>
+      <dt><a href="{% host_url 'dashboard-index' host 'dashboard' %}">{% translate "Development Dashboard" %}</a></dt>
       <dd>{% translate "Statistics about Django development" %}</dd>
       <dt><a href="https://groups.google.com/group/django-updates">{% translate "django-updates Mailing List" %}</a></dt>
       <dd>{% translate "Get updated for each code and ticket change" %}</dd>
@@ -57,9 +57,9 @@ <h3>{% translate "More Links" %}</h3>
       <dd>{% translate "Find third-party packages to supercharge your project" %}</dd>
       <dt><a href="https://builtwithdjango.com/projects/" rel="nofollow">{% translate "Django-powered Sites" %}</a></dt>
       <dd>{% translate "Add your site to the list" %}</dd>
-      <dt><a href="/community/badges/">{% translate "Django Badges" %}</a></dt>
+      <dt><a href="{% host_url "homepage" host "www" %}community/badges/">{% translate "Django Badges" %}</a></dt>
       <dd>{% translate "Show your support (or wish longingly)" %}</dd>
-      <dt><a href="/community/logos/">{% translate "Django Logos" %}</a></dt>
+      <dt><a href="{% host_url "homepage" host "www" %}community/logos/">{% translate "Django Logos" %}</a></dt>
       <dd>{% translate "Download official logos" %}</dd>
     </dl>
   </div>
diff --git a/djangoproject/templates/base_foundation.html b/djangoproject/templates/base_foundation.html
index 3925eb316c..e178749093 100644
--- a/djangoproject/templates/base_foundation.html
+++ b/djangoproject/templates/base_foundation.html
@@ -1,5 +1,5 @@
 {% extends "base.html" %}
-{% load fundraising_extras meetings i18n %}
+{% load fundraising_extras meetings i18n hosts %}
 
 {% block og_title %}Django Software Foundation{% endblock %}
 
@@ -19,11 +19,11 @@ <h2 class="visuallyhidden" id="aside-header">{% translate "Additional Informatio
 
     <h3>About the foundation</h3>
     <ul class="list-links">
-      <li><a href="/foundation/faq/">FAQ</a></li>
-      <li><a href="/foundation/records/">Records</a></li>
+      <li><a href="{% host_url 'homepage' host 'www' %}foundation/faq/">FAQ</a></li>
+      <li><a href="{% host_url 'homepage' host 'www' %}foundation/records/">Records</a></li>
       <li><a href="{% url 'contact_foundation' %}">Contact us</a></li>
-      <li><a href="/foundation/cla/">Contributor license agreements</a></li>
-      <li><a href="/foundation/conferences/">Organizing a Django conference</a></li>
+      <li><a href="{% host_url 'homepage' host 'www' %}foundation/cla/">Contributor license agreements</a></li>
+      <li><a href="{% host_url 'homepage' host 'www' %}foundation/conferences/">Organizing a Django conference</a></li>
     </ul>
     <h3>{% translate "Latest DSF meeting minutes" %}</h3>
     <p> {% translate "The minutes from May 2025 onwards are stored in the repo" %}
diff --git a/djangoproject/templates/base_weblog.html b/djangoproject/templates/base_weblog.html
index dc672dc2a3..08c975e719 100644
--- a/djangoproject/templates/base_weblog.html
+++ b/djangoproject/templates/base_weblog.html
@@ -1,5 +1,5 @@
 {% extends "base.html" %}
-{% load fundraising_extras i18n weblog %}
+{% load fundraising_extras i18n weblog hosts %}
 {% block layout_class %}sidebar-right{% endblock %}
 {% block title %}{% translate "News &amp; Events" %}{% endblock %}
 
@@ -34,7 +34,7 @@ <h3>{% translate "Upcoming Events" %}</h3>
         {% endfor %}
       </ul>
     {% endif %}
-    <p><a href="/foundation/conferences/">{% translate "Want your event listed here?" %}</a></p>
+    <p><a href="{% host_url 'homepage' host 'www' %}foundation/conferences/">{% translate "Want your event listed here?" %}</a></p>
 
     {% comment %}
     {# tags not implemented in backend yet #}
diff --git a/djangoproject/templates/fundraising/index.html b/djangoproject/templates/fundraising/index.html
index c470f15537..fe3d19e428 100644
--- a/djangoproject/templates/fundraising/index.html
+++ b/djangoproject/templates/fundraising/index.html
@@ -1,5 +1,5 @@
 {% extends 'base.html' %}
-{% load fundraising_extras humanize i18n static %}
+{% load fundraising_extras humanize i18n static hosts %}
 
 {% block title %}{% translate "Support Django" %}{% endblock %}
 {% block layout_class %}full-width{% endblock %}
@@ -42,8 +42,9 @@ <h2>{% translate "Other ways to give" %}</h2>
     </li>
     <li><a href="https://github.com/sponsors/django" target="_blank">{% translate "Sponsor Django via GitHub Sponsors" %}</a>.</li>
     <li>
+      {% url 'fundraising:index' as fundraising_url %}
       {% blocktranslate trimmed %}
-        <a href="/foundation/donate/#benevity-giving">Benevity Workplace Giving
+        <a href="{{ fundraising_url }}#benevity-giving">Benevity Workplace Giving
           Program</a> - If your employer participates, you can make donations to the
         DSF via payroll deduction.
       {% endblocktranslate %}
@@ -89,7 +90,7 @@ <h2 id="why-give">{% translate "Why give to the Django Software Foundation?" %}<
 
   <p>
     {% blocktranslate trimmed %}
-      Still curious? See our <a href="/foundation/donate/">Frequently Asked Questions</a>
+      Still curious? See our <a href="{{ fundraising_url }}">Frequently Asked Questions</a>
       about donations.
     {% endblocktranslate %}
   </p>
@@ -118,12 +119,13 @@ <h2 id="fellowship-program">{% translate "Django Fellowship Program" %}</h2>
   </p>
 
   <p>
+    {% host_url 'homepage' host 'www' as base_url %}
     {% blocktranslate trimmed %}
       For more details, you can read retrospectives for the
-      <a href="/weblog/2015/jan/21/django-fellowship-retrospective/"> first three
+      <a href="{{ base_url }}weblog/2015/jan/21/django-fellowship-retrospective/"> first three
         months of the program</a>,
-      <a href="/weblog/2015/dec/17/fellowship-2015-retrospective/">2015</a>, and
-      <a href="/weblog/2016/dec/28/fellowship-2016-retrospective/">2016</a>.
+      <a href="{{ base_url }}weblog/2015/dec/17/fellowship-2015-retrospective/">2015</a>, and
+      <a href="{{ base_url }}weblog/2016/dec/28/fellowship-2016-retrospective/">2016</a>.
     {% endblocktranslate %}
   </p>
 
@@ -144,7 +146,7 @@ <h2 id="fellowship-program">{% translate "Django Fellowship Program" %}</h2>
   <p>
     {% blocktranslate trimmed %}
       <strong>If you use Django on a daily basis and care about the development of Django
-        itself, you should donate today</strong> (may be <a href="/foundation/donate/#tax-deductible">tax deductible</a>).
+        itself, you should donate today</strong> (may be <a href="{{ fundraising_url }}#tax-deductible">tax deductible</a>).
       Only with your support can we make sure that the web framework you base your work on
       can grow to be even better in the coming years.
     {% endblocktranslate %}
@@ -249,15 +251,16 @@ <h2 id="dsf-supporters">{% translate "DSF Supporters" %}</h2>
   <div class="layout-tertiary" id="about">
     <div class="container">
       <h2>{% translate "What is the Django Software Foundation?" %}</h2>
+      {% host_url 'homepage' host 'www' as base_url %}
       <p>
         {% blocktranslate trimmed %}
           Development of Django is supported by an independent foundation
           established as a 501(c)(3) non-profit. Like most open-source foundations,
-          the goal of the <a href="/foundation/">Django Software Foundation</a>
+          the goal of the <a href="{{ base_url }}foundation/">Django Software Foundation</a>
           is to promote, support, and advance the Django web framework. If you're
           interested in how the Django Software Foundation supports the Django
           web framework, we published a
-          <a href="/weblog/2015/jan/08/django-software-foundation-2014/">
+          <a href="{{ base_url }}weblog/2015/jan/08/django-software-foundation-2014/">
             Summary of 2014.
           </a>
         {% endblocktranslate %}
@@ -274,7 +277,7 @@ <h2 id="who-are-the-django-fellows">{% translate "Who are the Django Fellows?" %
           team since 2021 and a core committer to Python projects such as
           music21, pylint, and <a href="https://archesproject.org/">Arches</a>.
           Jacob
-          <a href="https://www.djangoproject.com/weblog/2025/aug/11/welcome-our-new-fellow-jacob-tyler-walls/">
+          <a href="{{ base_url }}weblog/2025/aug/11/welcome-our-new-fellow-jacob-tyler-walls/">
             began as a full-time Fellow in August 2025</a>.
         {% endblocktranslate %}
       </p>
@@ -285,7 +288,7 @@ <h2 id="who-are-the-django-fellows">{% translate "Who are the Django Fellows?" %
             (2024-present)</strong> - an active community member, co-creator of
           <a href="https://djangonaut.space">Djangonaut Space</a> and a member of
           Django's review and triage team since 2023. Sarah
-          <a href="https://www.djangoproject.com/weblog/2024/mar/22/welcome-our-new-fellow-sarah-boyce/">
+          <a href="{{ base_url }}weblog/2024/mar/22/welcome-our-new-fellow-sarah-boyce/">
             began as a full-time Fellow in April 2024</a>.
         {% endblocktranslate %}
       </p>
@@ -297,7 +300,7 @@ <h2 id="who-are-the-django-fellows">{% translate "Who are the Django Fellows?" %
           experience in architecting, building, and maintaining scalable web
           services, as well as leading new feature design and development.
           Natalia
-          <a href="https://www.djangoproject.com/weblog/2023/mar/31/welcome-our-new-fellow-natalia-bidart/">
+          <a href="{{ base_url }}weblog/2023/mar/31/welcome-our-new-fellow-natalia-bidart/">
             began as a part-time Fellow in April 2023</a>.
         {% endblocktranslate %}
       </p>
diff --git a/djangoproject/templates/homepage.html b/djangoproject/templates/homepage.html
index 3b1ad6b62e..23375bb473 100644
--- a/djangoproject/templates/homepage.html
+++ b/djangoproject/templates/homepage.html
@@ -1,5 +1,5 @@
 {% extends "base_3col.html" %}
-{% load fundraising_extras i18n weblog %}
+{% load fundraising_extras i18n weblog hosts %}
 
 {% block sectionid %}homepage{% endblock %}
 {% block body_class %}homepage{% endblock %}
@@ -141,7 +141,7 @@ <h3>{% translate "Get involved" %}</h3>
       <dd>
         {% translate "Report bugs and make feature requests" %}
       </dd>
-      <dt><a href="https://dashboard.djangoproject.com/">{% translate "Development dashboard" %}</a></dt>
+      <dt><a href="{% host_url 'dashboard-index' host 'dashboard' %}">{% translate "Development dashboard" %}</a></dt>
       <dd>
         {% translate "see what's currently being worked on" %}
       </dd>
@@ -163,20 +163,20 @@ <h3>{% translate "Get Help" %}</h3>
 
     <h3>{% translate "The Django Software Foundation" %}</h3>
     <dl class="list-links-small">
-      <dt><a href="/foundation/">{% translate "About the Foundation" %}</a></dt>
+      <dt><a href="{% host_url "homepage" host "www" %}foundation/">{% translate "About the Foundation" %}</a></dt>
       <dd>
         {% translate "Our non-profit supports the project" %}
       </dd>
 
-      <dt><a href="/foundation/donate/">{% translate "Support Django" %}</a></dt>
+      <dt><a href="{% url 'fundraising:index' %}">{% translate "Support Django" %}</a></dt>
       <dd>
         {% translate "Your contribution makes Django stronger" %}
       </dd>
 
-      <dt><a href="/contact/foundation/">{% translate "Contact the Django Software Foundation" %}</a></dt>
+      <dt><a href="{% host_url "homepage" host "www" %}contact/foundation/">{% translate "Contact the Django Software Foundation" %}</a></dt>
       <dd></dd>
     </dl>
-    <a href="/foundation/" class="link-readmore">{% translate "More about the DSF" %}</a>
+    <a href="{% host_url "homepage" host "www" %}foundation/" class="link-readmore">{% translate "More about the DSF" %}</a>
       {% comment %}
       <h3>Upcoming Events</h3>
       <dl class="list-links-small news-list">
diff --git a/djangoproject/templates/includes/footer.html b/djangoproject/templates/includes/footer.html
index ba995ba26b..12d613fdc4 100644
--- a/djangoproject/templates/includes/footer.html
+++ b/djangoproject/templates/includes/footer.html
@@ -60,9 +60,9 @@ <h3>Follow Us</h3>
           <h3>Support Us</h3>
           <ul>
             <li><a href="{% url "fundraising:index" %}">Sponsor Django</a></li>
-            <li><a href="{% host_url "homepage" host "www" %}foundation/corporate-membership/">Corporate membership</a></li>
+            <li><a href="{% url 'members:corporate-members' %}">Corporate membership</a></li>
             <li><a href="https://django.threadless.com/" target="_blank">Official merchandise store</a></li>
-            <li><a href="{% host_url "homepage" host "www" %}foundation/donate/#benevity-giving">Benevity Workplace Giving Program</a></li>
+            <li><a href="{% url 'fundraising:index' %}#benevity-giving">Benevity Workplace Giving Program</a></li>
           </ul>
         </div>
       </div>
@@ -82,9 +82,9 @@ <h3>Support Us</h3>
           <span class="ampersand">&amp;</span> <a class="andrevv" href="http://andrevv.com/">andrevv</a></li>
       </ul>
       <p class="copyright">&copy; 2005-{% now "Y" %}
-        <a href="{% url 'homepage' %}foundation/"> Django Software
+        <a href="{% host_url "homepage" host "www" %}foundation/"> Django Software
           Foundation</a> and individual contributors. Django is a
-        <a href="{% url 'homepage' %}trademarks/">registered
+        <a href="{% host_url "homepage" host "www" %}trademarks/">registered
           trademark</a> of the Django Software Foundation.
       </p>
     </div>
diff --git a/djangoproject/templates/members/corporate_member_badges.html b/djangoproject/templates/members/corporate_member_badges.html
index 5751065609..b4268a3abe 100644
--- a/djangoproject/templates/members/corporate_member_badges.html
+++ b/djangoproject/templates/members/corporate_member_badges.html
@@ -30,8 +30,9 @@
 {% block content %}
   <h1>{% translate "Corporate member badges" %}</h1>
   <p>
+    {% url 'members:corporate-members' as corporate_members_url %}
     {% blocktranslate trimmed %}
-      <a href="/foundation/corporate-membership/">Corporate members</a> of the Django Software Foundation may display
+      <a href="{{ corporate_members_url }}">Corporate members</a> of the Django Software Foundation may display
       these badges on their site to show their support.
     {% endblocktranslate %}
   </p>
diff --git a/djangoproject/templates/members/corporatemember_list.html b/djangoproject/templates/members/corporatemember_list.html
index 6085ca1877..513e58a954 100644
--- a/djangoproject/templates/members/corporatemember_list.html
+++ b/djangoproject/templates/members/corporatemember_list.html
@@ -1,5 +1,5 @@
 {% extends "base_foundation.html" %}
-{% load humanize i18n %}
+{% load humanize i18n hosts %}
 
 {% block og_title %}{% translate "Corporate members" %}{% endblock %}
 {% block og_description %}{% translate "The following organizations are corporate members of the Django Software Foundation." %}{% endblock %}
@@ -7,10 +7,11 @@
 {% block content %}
   <h1>{% translate "Corporate members" %}</h1>
   <p>
+    {% host_url 'homepage' host 'www' as base_url %}
     {% blocktranslate trimmed %}
       The following organizations are corporate members of the Django Software
       Foundation. If you are interested in becoming a corporate member of the
-      DSF, you can find out more on our <a href="/foundation/corporate-membership/">
+      DSF, you can find out more on our <a href="{{ base_url }}foundation/corporate-membership/">
         corporate membership page</a>.
     {% endblocktranslate %}
   </p>
diff --git a/djangoproject/templates/members/team_list.html b/djangoproject/templates/members/team_list.html
index acb43e4f59..5f06a4cd7b 100644
--- a/djangoproject/templates/members/team_list.html
+++ b/djangoproject/templates/members/team_list.html
@@ -15,6 +15,7 @@
 
   <h2>{% translate "Teams" %}</h2>
   <p>
+    {% url 'document-detail' lang='en' version='dev' url='internals/organization' host 'docs'  as organization_url %}
     {% blocktranslate trimmed %}
       The following teams are groups of people who support the Django project
       and the Django Software Foundation. Apart from the Django Fellows, who
@@ -24,7 +25,7 @@ <h2>{% translate "Teams" %}</h2>
       individuals with elevated permissions rather than formal teams. For an
       overview of how the Django Project is organized and the principles that
       guide it, see the
-      <a href="https://docs.djangoproject.com/en/dev/internals/organization/#organization-of-the-django-project">
+      <a href="{{ organization_url }}#organization-of-the-django-project">
         organization and principles
       </a> page.
     {% endblocktranslate %}
diff --git a/djangoproject/templates/releases/download.html b/djangoproject/templates/releases/download.html
index 21d31c81a2..52c8355ccc 100644
--- a/djangoproject/templates/releases/download.html
+++ b/djangoproject/templates/releases/download.html
@@ -71,7 +71,7 @@ <h2 id="supported-versions">Supported Versions</h2>
   <p>Certain feature releases will be designated as <strong>long-term support
     (LTS) releases</strong>. These releases will get security and data loss
     fixes applied for a guaranteed period of time, typically three years.</p>
-  <p>See the <a href="https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions">
+  <p>See the <a href="{% url 'document-detail' lang='en' version='dev' url='internals/release-process' host 'docs' %}#supported-versions">
     supported versions policy</a> for detailed guidelines about what fixes will be backported.</p>
 
   <img src="{% static "img/release-roadmap.png" %}" class='img-release' style="max-width:100%;" alt="Django release roadmap">
diff --git a/djangoproject/templates/releases/roadmap.html b/djangoproject/templates/releases/roadmap.html
index 42095cbe77..20214392c5 100644
--- a/djangoproject/templates/releases/roadmap.html
+++ b/djangoproject/templates/releases/roadmap.html
@@ -1,5 +1,5 @@
 {% extends "base.html" %}
-{% load date_format fundraising_extras %}
+{% load date_format fundraising_extras hosts %}
 
 {% block sectionid %}roadmap{% endblock %}
 {% block title %}Django {{ series }} Roadmap{% endblock %}
@@ -21,11 +21,11 @@ <h2>What features will be in Django {{ series }}?</h2>
       that miss the deadline won't.</p>
     <p>If you have a major feature you'd like to contribute, please propose it on
       <a href="https://github.com/orgs/django/projects/24/">new feature ideas GitHub project</a> and review the
-      <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#requesting-features">requesting features documentation</a>.</p>
+      <a href="{% url 'document-detail' lang='en' version='dev' url='internals/contributing/bugs-and-features' host 'docs' %}#requesting-features">requesting features documentation</a>.</p>
     <p>Minor features and bug fixes will be merged as they are completed. If you
       have submitted a patch, ensure the flags on the Trac ticket are correct so it
       appears in the "Patches needing review" filter of the
-      <a href="https://dashboard.djangoproject.com/">Django Development Dashboard</a>.
+      <a href="{% host_url 'dashboard-index' host 'dashboard' %}">Django Development Dashboard</a>.
       Better yet, find someone to review your patch and mark the ticket as
       "Ready for checkin". Tickets marked "Ready for checkin" are regularly reviewed
       by mergers.</p>
@@ -35,9 +35,9 @@ <h2>What features will be in Django {{ series }}?</h2>
     <h2>How you can help</h2>
     <p>Community effort is key. You can help by:</p>
     <ul>
-      <li>Reading the <a href="http://docs.djangoproject.com/en/dev/internals/contributing/">guide to contributing</a>
-        and <a href="http://docs.djangoproject.com/en/dev/internals/release-process/">Django's release process</a>.</li>
-      <li>Working on patches and <a href="https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/">triaging tickets</a>.</li>
+      <li>Reading the <a href="{% url 'document-detail' lang='en' version='dev' url='internals/contributing' host 'docs' %}">guide to contributing</a>
+        and <a href="{% url 'document-detail' lang='en' version='dev' url='internals/release-process' host 'docs' %}">Django's release process</a>.</li>
+      <li>Working on patches and <a href="{% url 'document-detail' lang='en' version='dev' url='internals/contributing/triaging-tickets' host 'docs' %}">triaging tickets</a>.</li>
       <li>Attending sprints.</li>
       <li>Testing release snapshots (alphas, betas) against your code and reporting bugs.</li>
       <li>Providing as many testers as possible to ensure a bug-free release.</li>
diff --git a/docs/templates/docs/doc.html b/docs/templates/docs/doc.html
index 2373d2114a..099c10507e 100644
--- a/docs/templates/docs/doc.html
+++ b/docs/templates/docs/doc.html
@@ -191,7 +191,7 @@ <h3 id="getting-help-sidebar">{% trans "Getting help" %}</h3>
           <dt><a href="{% url 'document-detail' lang=lang version=version url="faq" host 'docs' %}">{% trans "FAQ" %}</a></dt>
           <dd>{% blocktrans %}Try the FAQ — it's got answers to many common questions.{% endblocktrans %}</dd>
 
-          <dt><a href="/en/stable/genindex/">{% trans "Index" %}</a>, <a href="/en/stable/py-modindex/">{% trans "Module Index" %}</a>, or <a href="/en/stable/contents/">{% trans "Table of Contents" %}</a></dt>
+          <dt><a href="{% url 'document-detail' lang='en' version='stable' url='genindex' host 'docs' %}">{% trans "Index" %}</a>, <a href="{% url 'document-detail' lang='en' version='stable' url='py-modindex' host 'docs' %}">{% trans "Module Index" %}</a>, or <a href="{% url 'document-detail' lang='en' version='stable' url='contents' host 'docs' %}">{% trans "Table of Contents" %}</a></dt>
           <dd>{% blocktrans %}Handy when looking for specific information.{% endblocktrans %}</dd>
 
           <dt><a href="https://chat.djangoproject.com">{% trans "Django Discord Server" %}</a></dt>
diff --git a/members/forms.py b/members/forms.py
index 095edcb605..3124ae7b9c 100644
--- a/members/forms.py
+++ b/members/forms.py
@@ -53,7 +53,7 @@ def __init__(self, *args, **kwargs):
         )
         self.fields["description"].help_text = _(
             """We'll use this text on the
-            <a href="/foundation/corporate-members/">
+            <a href="https://www.djangoproject.com/foundation/corporate-members/">
             corporate membership page</a>; you can use the existing descriptions
             as a guide for flavor we're looking for."""
         )
@@ -67,9 +67,9 @@ def __init__(self, *args, **kwargs):
         self.fields["amount"].help_text = _(
             """Enter an amount above and the appropriate membership level will
             be automatically selected. Or select a membership level below and
-            the minimum donation will be entered for you. See
-            <a href="/foundation/corporate-membership/#dues">dues</a> for
-            details on the levels."""
+            the minimum donation will be entered for you. See <a
+            href="https://www.djangoproject.com/foundation/corporate-membership/#dues"
+            >dues</a> for details on the levels."""
         )
 
     class Meta:
diff --git a/releases/tests.py b/releases/tests.py
index da7d893f2c..a3553d1f89 100644
--- a/releases/tests.py
+++ b/releases/tests.py
@@ -688,11 +688,5 @@ def test_major_lower_bound(self):
     def test_links_to_contributing_and_release_process_present(self):
         url = reverse("roadmap", kwargs={"series": "20.0"})
         response = self.client.get(url)
-        self.assertContains(
-            response,
-            'href="http://docs.djangoproject.com/en/dev/internals/contributing/"',
-        )
-        self.assertContains(
-            response,
-            'href="http://docs.djangoproject.com/en/dev/internals/release-process/"',
-        )
+        self.assertContains(response, 'en/dev/internals/contributing/"')
+        self.assertContains(response, 'en/dev/internals/release-process/"')