Put hyperlinks around tags, remove hard coded guidelines from the review page,...

Put hyperlinks around tags, remove hard coded guidelines from the review page, but refer to the new sponsor page instead

debexpo/templates/index/reviewers.mako

@@ -32,13 +32,4 @@
 
 <h3>Established sponsor guidelines</h3>
 
-<p>Several Debian Developers published their personal sponsor guidelines. Those are rules applying for a particular person or a specific packaging team in case you want to have a package sponsored by them. Typically those rules extend the Debian policy by custom requirements, or require a particular workflow from you. You can have a look at some guidelines from different people here</p>
-
-<ul>
-    <li><a href="http://wiki.debian.org/PaulWise/Standards">Paul Wise</a></li>
-    <li><a href="http://people.debian.org/~codehelp/#sponsor">Neil Williams</a></li>
-    <li><a href="http://wiki.debian.org/KilianKrause">Kilian Krause</a></li>
-    <li><a href="http://people.debian.org/~neilm/sponsorship.html">Neil McGovern</a></li>
-    <li><a href="http://wiki.debian.org/Games/Checklist">Debian games team</a></li>
-    <li>More guidelines in the wiki: <a href="http://wiki.debian.org/SponsorChecklist">SponsorChecklist</a></li>
-</ul>
+<p>Several Debian Developers published their personal sponsor guidelines. Those are rules applying for a particular person or a specific packaging team in case you want to have a package sponsored by them. Typically those rules extend the Debian policy by custom requirements, or require a particular workflow from you. You can have a look at some guidelines from different people on our ${ h.tags.link_to( _('sponsors side'), h.url('sponsors')) }</p>

debexpo/templates/sponsor/index.mako

@@ -39,12 +39,12 @@ To help you finding a sponsor interested in your package, they can formulate spo
 
 <%def name="tag_helper(requirement)">
     % if not c.sponsor_filter:
-        <dt>${ requirement.label } (${ h.tags.link_to(  _('Filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
+        <dt id="${requirement.tag}">${ requirement.label } (${ h.tags.link_to(  _('Filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
         <dd>${ requirement.long_description | n}</dd>
     % elif requirement.tag not in c.sponsor_filter:
-        <dt><span style="text-decoration: line-through;">${ requirement.label }</span> (${ h.tags.link_to(  _('Add to filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
+        <dt><span id="${requirement.tag}" style="text-decoration: line-through;">${ requirement.label }</span> (${ h.tags.link_to(  _('Add to filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
     % else:
-        <dt>${ requirement.label } (${ h.tags.link_to(  _('Remove filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
+        <dt id="${requirement.tag}">${ requirement.label } (${ h.tags.link_to(  _('Remove filter'), h.url.current(action='toggle', tag=requirement.tag))  })</dt>
         <dd>${ requirement.long_description | n}</dd>
     % endif
 </%def>
@@ -138,7 +138,7 @@ To help you finding a sponsor interested in your package, they can formulate spo
         <td>
             <ul>
             % for requirement in sponsor.get_technical_tags_full():
-                    <li>${ requirement.label }</li>
+                    <li>${ h.tags.link_to( requirement.label, h.url.current(anchor=requirement.tag) )}</li>
             % endfor
             </ul>
             <p>${ sponsor.get_guidelines() | n}</p>
@@ -146,7 +146,7 @@ To help you finding a sponsor interested in your package, they can formulate spo
         <td>
             <ul>
             % for requirement in sponsor.get_social_tags_full():
-                    <li>${ requirement.label }</li>
+                    <li>${ h.tags.link_to( requirement.label, h.url.current(anchor=requirement.tag) )}</li>
             % endfor
             </ul>
             ${ sponsor.get_social_requirements() | n}