feat: remove directory page links

templates/legal/contributors/faq.html

@@ -20,7 +20,7 @@ <h3 id="new-copies">Do I have to send a new copy of the agreement for each proje
       <h3 id="why-two">Why are there two separate documents, one for individuals and one for companies?</h3>
       <p>The two are mostly the same. Individuals may be minors or they might need permission from their employer, while companies need to think about their affiliates.</p>
       <h3 id="previous-agreement">Didn't Canonical previously use a different agreement?</h3>
-      <p>Yes, up until July 2011 we used the Canonical Contributor Agreement 2.5. With the launch of the <a href="http://harmonyagreements.org/">Harmony contributor agreements</a>, we decided to switch to one of their standard templates, a Harmony Contributor licence agreement. The <a href="https://assets.ubuntu.com/v1/ea46173e-Canonical_Contributor_Agreement_ver_2.5.pdf">old agreement</a> is still available for reference, but we are not asking for anyone new to sign it.</p>
+      <p>Yes, up until July 2011 we used the Canonical Contributor Agreement 2.5. With the launch of the <a href="https://harmonyagreements.org/">Harmony contributor agreements</a>, we decided to switch to one of their standard templates, a Harmony Contributor licence agreement. The <a href="https://assets.ubuntu.com/v1/ea46173e-Canonical_Contributor_Agreement_ver_2.5.pdf">old agreement</a> is still available for reference, but we are not asking for anyone new to sign it.</p>
       <h3 id="re-sign">If I signed the old agreement, do I need to sign the new one too?</h3>
       <p>No. If you previously accepted the Canonical Contributor Agreement 2.5 (or earlier), your future contributions will continue to be covered by that. However, if you wish, you can sign the new Contributor licence agreement, in which case the terms of the new agreement will cover any new contributions.</p>
       <h3 id="old-new-difference">What's the difference between the new agreement and the old one?</h3>
@@ -30,17 +30,8 @@ <h3 id="who-owns-copyright">Who owns the copyright?</h3>
       <p>"You retain ownership of the Copyright in Your Contribution and have the same rights to use or license the Contribution which You would have had without entering into the Agreement."</p>
       <h3 id="other-projects">Can I contribute the same code to other projects as well?</h3>
       <p>Yes. You retain the full rights to redistribute your own code as you wish. The agreement is not exclusive and you may contribute what you write to as many other projects or organisations as you wish to share it with.</p>
-      <h3 id="other-questions">What if I have other questions?</h3>
-      <p>The best person to ask is the coordinator for the project you're contributing to. All the coordinators are listed on the main <a href="http://www.canonical.com/projects/directory">open source projects directory</a>.</p>
     </div>
     <div class="col-4">
-      <div class="p-card">
-        <h3>Related content</h3>
-        <ul class="p-list">
-          <li class="p-list__item"><a href="http://www.canonical.com/projects/directory">Open source software projects</a></li>
-        </ul>
-      </div>
-
       <div class="p-card">
         <h3>Additional information</h3>
         <ul class="p-list">

templates/legal/contributors/index.html

@@ -9,8 +9,8 @@
   <div class="row">
     <div class="col-8">
       <h1>Canonical contributor licence&nbsp;agreement</h1>
-      <p>At Canonical, we manage a lot of <a href="http://www.canonical.com/projects/directory">open source projects</a> and we're required to have agreements with everyone who takes part in them. It's the easiest way for you to give us permission to use your contributions. In effect, you're giving us a licence, but you still own the copyright &mdash; so you retain the right to modify your code and use it in other projects. </p>
-      <p>Several upstream projects require all contributors to agree on the rules for inclusion of their code, we encourage Ubuntu members to support those when working with the upstream on contribution of patches back to those projects or direct contributions. For most <a href="http://www.canonical.com/projects/directory">projects at Canonical</a>, the preferred approach is a wide licence rather than an assignment of ownership, and the agreements are documented below. Other projects take their own view but we typically recommend supporting their preferred approach to contribution and licensing, whatever that might be.</p>
+      <p>At Canonical, we manage a lot of open source projects and we're required to have agreements with everyone who takes part in them. It's the easiest way for you to give us permission to use your contributions. In effect, you're giving us a licence, but you still own the copyright &mdash; so you retain the right to modify your code and use it in other projects. </p>
+      <p>Several upstream projects require all contributors to agree on the rules for inclusion of their code, we encourage Ubuntu members to support those when working with the upstream on contribution of patches back to those projects or direct contributions. For most projects at Canonical, the preferred approach is a wide licence rather than an assignment of ownership, and the agreements are documented below. Other projects take their own view but we typically recommend supporting their preferred approach to contribution and licensing, whatever that might be.</p>
     </div>
     <div class="col-4">
       <div class="u-align--center">