www/server/staging/standards gnu-website-guidel...

[Therese Godefroy]

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 21/02/25 07:32:39

Modified files:
        server/staging/standards: gnu-website-guidelines.html 

Log message:
        [WIP] Reorganize the 'URLs' section.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.28&r2=1.29

Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /webcvs/www/www/server/staging/standards/gnu-website-guidelines.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- gnu-website-guidelines.html 25 Feb 2021 11:29:18 -0000      1.28
+++ gnu-website-guidelines.html 25 Feb 2021 12:32:38 -0000      1.29
@@ -342,7 +342,7 @@
 </ul>
 
 
-<h4 id="urls">URLs</h4>
+<h4 id="urls">URLs - Local links and anchors</h4>
 
 <ul class="para">
 <li>Hand-written URLs that refer to other files on www.gnu.org should be
@@ -355,13 +355,6 @@
 <code>http://www.gnu.org/</code> will be wrong when the visitor uses
 HTTPS.</li>
 
-<li>Check if the linked host supports HTTPS and always prefer HTTPS over HTTP
-when the former is supported and has a valid certificate (this is expressed by
-a locked/green lock on most web browsers).</li>
-
-<li>Protocol-relative URLs (e.g., <code>//www.example.org</code>) are not
-recommended when linking to external, third-party domains.</li>
-
 <li>Collections of files produced automatically from Texinfo source
 contain links with relative file names.  They always refer to another
 file in the same directory.  These relative links are to be
@@ -399,6 +392,34 @@
 Please avoid moving the old <code>id</code> to a translatable string.
 Translators will thank you!</li>
 
+<li>When embedding static resources like videos that are not in
+the <code>www</code> CVS repository along with the rest of the
+www.gnu.org pages, it's important that the URL used to embed the asset
+be a subdomain of gnu.org, so that the Third-party Request Blocker
+add-on shipped with GNU IceCat would not consider it a third-party
+asset which it would prevent from being loaded.  For example, when
+embedding videos from FSF campaigns on www.gnu.org, use
+<code>static.gnu.org</code> rather than <code>static.fsf.org</code>.
+Both of these addresses have been set to point to the same machine, so
+they can be used interchangeably.</li>
+</ul>
+
+
+<h4 id="external-links">URLs - External links</h4>
+
+<ul class="para">
+<li>Check if the linked host supports HTTPS and always prefer HTTPS over HTTP
+when the former is supported and has a valid certificate (this is expressed by
+a locked/green lock on most web browsers).</li>
+
+<li>Protocol-relative URLs (e.g., <code>//www.example.org</code>) are not
+recommended when linking to external, third-party domains.</li>
+</ul>
+
+
+<h4 id="mailto">URLs - Email links</h4>
+
+<ul class="para">
 <li>Place angle brackets around <code>mailto:</code> anchors (which will
 bring up a mail form to fill out and send, if this is supported by the
 client) to clearly distinguish them from hypertext links.  See
@@ -422,17 +443,6 @@
 </p>
 <p>If the person doesn't have a web page, leave the name unanchored.</p>
 </li>
-
-<li>When embedding static resources like videos that are not in
-the <code>www</code> CVS repository along with the rest of the
-www.gnu.org pages, it's important that the URL used to embed the asset
-be a subdomain of gnu.org, so that the Third-party Request Blocker
-add-on shipped with GNU IceCat would not consider it a third-party
-asset which it would prevent from being loaded.  For example, when
-embedding videos from FSF campaigns on www.gnu.org, use
-<code>static.gnu.org</code> rather than <code>static.fsf.org</code>.
-Both of these addresses have been set to point to the same machine, so
-they can be used interchangeably.</li>
 </ul>
 
 
@@ -1326,7 +1336,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/02/25 11:29:18 $
+$Date: 2021/02/25 12:32:38 $
 <!-- timestamp end --></p>
 </div>
 </div><!-- for class="inner", starts in the banner include -->