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

[Ineiev]

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 21/02/11 07:08:01

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

Log message:
        Revert TOC to current style, drop obsolete and unapplicable notes, 
amend markup.

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

Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /web/www/www/server/staging/standards/gnu-website-guidelines.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- gnu-website-guidelines.html 10 Feb 2021 13:26:50 -0000      1.7
+++ gnu-website-guidelines.html 11 Feb 2021 12:08:01 -0000      1.8
@@ -15,7 +15,7 @@
 </p>
 
 <h3 class="no-display">Table of Contents</h3>
-<ol class="summary">
+<ul class="summary">
   <li><a href="#GeneralGuidelines">General Guidelines</a></li>
   <li><a href="#CopyrightGuidelines">Copyright Guidelines</a></li>
   <li><a href="#orthography">Spelling and Punctuation</a></li>
@@ -37,18 +37,18 @@
     </ul>
   </li>
   <li><a href="#UsefulResources">Useful Resources</a></li>
-</ol>
+</ul>
 <hr class="no-display" />
 
 
 <p>Please be considerate of all who access our web pages, and accommodate
-them, including those who use devices with limited computing power, as well
+them, including those who use text-only browsers or old browsers, as well
 as those with slow connections. We wish to prevent web designs that look
 great under one version of one browser, and ugly under many others.  Of
 course, please don't install any of the proprietary web browsers
 available if you don't already use them anyway.</p>
 
-<h3 id="GeneralGuidelines">1. General Guidelines</h3>
+<h3 id="GeneralGuidelines">General Guidelines</h3>
 
 
 <ul>
@@ -102,17 +102,17 @@
 by the FSF.</li>
 
 <li>Generally, the use of JavaScript is not allowed.  Exceptions to
-this need to be reviewed and approved by the Chief GNUisance (RMS) on a
+this need to be reviewed and approved by the Chief GNUisance on a
 case-by-case basis.</li>
 </ul>
 
 
-<h3 id="CopyrightGuidelines">2. Copyright Guidelines</h3>
+<h3 id="CopyrightGuidelines">Copyright Guidelines</h3>
 
 
 <ul>
 <li>Every page should have a copyright notice.  See the <a
-href="https://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain";>
+href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain">
 boilerplate</a>, referred below.</li>
 
 <li>Every page should have a notice giving everyone permission
@@ -151,7 +151,7 @@
 </ul>
 
 
-<h3 id="orthography">3. Spelling and Punctuation</h3>
+<h3 id="orthography">Spelling and Punctuation</h3> 
 
 
 <ul>
@@ -177,7 +177,7 @@
 
 
 <a id="FilenameAndURLGuidelines"></a>
-<h3 id="filenames">4. Filenames</h3>
+<h3 id="filenames">Filenames</h3>
 
 
 <ul>
@@ -194,39 +194,31 @@
 
 <li id="NamingTranslations">If you translate your web page in different
 languages, please name the English file <code><var>article</var>.html</code>, 
and
-its translations <code><var>article.lang</var>.html</code>&mdash;
-<code><var>lang</var></code> should contain a code from <a
-href="https://www.loc.gov/standards/iso639-2/php/code_list.php";
-rel="noopener">ISO 639-1</a>,
-and optionally an hyphen followed by the <i>Alpha-2</i> country code given in
-<a href="https://www.iso.org/obp/ui/#search/code/";
-rel="noopener">ISO 3166-1</a>.
-For example, the German translation of <code>not-ipr.html</code>
+its translations <code><var>article</var>.<var>lang</var>.html</code>&mdash;
+<code><var>lang</var></code> should contain the two-letter language code from 
<a
+href="//www.loc.gov/standards/iso639-2/php/code_list.php">ISO 639</a>,
+and optionally an hyphen followed the two-letter country code given in
+ISO 3166.  For example, the German translation of <code>not-ipr.html</code>
 should be named <code>not-ipr.de.html</code>; the Brazilian Portuguese
 translation should be named <code>not-ipr.pt-br.html</code>.</li>
 </ul>
 
 
-<h3 id="urls">5. URLs</h3>
+<h3 id="urls">URLs</h3>
 
 
 <ul>
 <li>Hand-written URLs that refer to other files on www.gnu.org should be
 absolute, starting from the root page.  That is, paths should start
 with <code>/</code> (e.g., <code>/gnu/about-gnu.html</code>; <em>not</em>
-<code>http://www.gnu.org/gnu/about-gnu.html</code> nor
-<code>https://gnu.org/gnu/about-gnu.html</code>, and <em>not</em>
+<code>http://www.gnu.org/gnu/about-gnu.html</code>, and <em>not</em>
 <code>about-gnu.html</code>).  This makes it easier to copy and paste
 links from other pages.  Besides, links like
 <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 3rd-party domains.</li>
+<li>Check if the linked host supports both HTTPS and HTTP and use
+protocol-relative URLs (e.g. <code>//www.example.org</code>) if it does.</li>
 
 <li>Collections of files produced automatically from Texinfo source
 contain links with relative file names.  They always refer to another
@@ -246,10 +238,8 @@
 <li>Be sure to omit the filename entirely when linking to an anchor in
 the same file and double-check that the anchor actually works.</li>
 
-<li>Consider others linking to your page when removing an <code>id</code>
-attribute from any header tag (<code>&lt;h1 id="example"&gt;&hellip;</code>,
-<code>&lt;h2&hellip;</code>, <code>&lt;h3&hellip;</code>, &hellip;) or
-anchor (e.g. <code>&lt;a id="example"&gt;#example&lt;/a&gt;</code>).</li>
+<li>Consider others linking to your page when removing an anchor or
+<code>id</code> attribute.</li>
 
 <li>We encourage FTP sites to use a directory for each package, and only put
 one package's files in each directory, so that the users can see what
@@ -259,25 +249,23 @@
 location URLs do not need to be changed, on this and other sites, as new
 versions are released into that directory.</li>
 
-<li>Cite people with e-mail addresses using the
-<a href="https://tools.ietf.org/html/rfc6068"; rel="noopener">RFC6068</a> 
syntax:
+<li><p>Cite people with e-mail addresses this way:</p>
 <p class="emph-box"><code>
-&lt;a href="https://www.stallman.org/"&gt;Richard Stallman&lt;/a&gt;
+&lt;a href="//www.stallman.org/"&gt;Richard Stallman&lt;/a&gt;
 &lt;a href="mailto:rms@gnu.org"&gt;&amp;lt;rms@gnu.org&amp;gt;&lt;/a&gt;
 </code></p>
-which browsers display this way:
+<p>which browsers display this way:</p>
 <p class="emph-box" style="background-color: inherit">
-  <a href="https://www.stallman.org/";>Richard Stallman</a>
-  <a href="mailto:rms@gnu.org";>&lt;rms@gnu.org&gt;</a>
+<a href="//www.stallman.org/">Richard Stallman</a>
+<a href="mailto:rms@gnu.org";>&lt;rms@gnu.org&gt;</a>
 </p>
-It is less confusing to the user, because it's clear what is a
-<code>https:</code> link to another web page and what is a
-<code>mailto:</code> anchor that
+<p>It is less confusing to the user, because it's clear what is a link
+to another web page and what is a <code>mailto:</code> anchor that
 will bring up a mail form to fill out and send, if this is
 supported by the client.  Also, if users save a copy of the page,
 they will have a copy of the e-mail address they can use without
 going back to their web browser.  If the person doesn't have a web
-page, leave the name unanchored.</li>
+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
@@ -292,21 +280,16 @@
 </ul>
 
 
-<h3 id="HTMLGuidelines">6. HTML Guidelines</h3>
+<h3 id="HTMLGuidelines">HTML Guidelines</h3>
 
 
 <ul>
-<li>HTML 5 and CSS3 are preferred over older (X)HTML and CSS standards.</li>
-
-<li>All markup on the GNU web server should be strictly compliant with
-<a href="https://www.w3.org/standards/";>W3C standards</a>.</li>
-
-<li>The subsets of HTML and CSS used must be composed only by official
-W3C Recommendations (RECs) and be supported by the most used web browsers.</li>
+<li>HTML on the GNU web server should be strictly compliant with
+<a href="//www.w3.org/standards/">W3C standards</a>.</li>
 
 <li>Please follow the above mentioned web standards strictly.  Don't
 neglect <a
-href="https://www.w3.org/TR/html401/struct/global.html#h-7.1";>required
+href="//www.w3.org/TR/html401/struct/global.html#h-7.1">required
 elements</a> such as <code>&lt;html&gt;</code>, <code>&lt;head&gt;</code>,
 <code>&lt;title&gt;</code>, <code>&lt;body&gt;</code>, etc. when using (X)HTML,
 and always include the appropriate DTD or Schema reference.
@@ -363,7 +346,7 @@
 </ul>
 
 
-<h3 id="tables">7. Tables and menus</h3>
+<h3 id="tables">Tables and menus</h3>
 
 
 <ul>
@@ -374,7 +357,7 @@
 from left to right, ignoring any tables that you make. If you use
 tables, you should make sure that reading a whole
 page left to right doesn't confuse such software.  Please follow the
-<a href="https://www.w3.org/WAI/";>W3C web accessibility guidelines</a>
+<a href="//www.w3.org/WAI/">W3C web accessibility guidelines</a>
 to ensure that tables are properly marked for accessibility.</li>
 
 <li>Some people like to organize links as a menu to
@@ -392,7 +375,7 @@
 </ul>
 
 
-<h3 id="templating">8. Using our page template</h3>
+<h3 id="templating">Using our page template</h3>
 
 
 <ul>
@@ -401,31 +384,26 @@
 website, and the software projects.  Its use is mandatory for new pages in
 www.gnu.org, and highly recommended for software pages.  Please don't start
 out with an existing page to create a new one; use the <a
-href="https://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain";>
+href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain">
 original source</a> of the boilerplate instead, and follow the instructions
 in it.</li>
 
 <li>The XHTML templated pages must follow the <a
-href="https://www.w3.org/TR/xhtml1/";>XHTML-1.0 guidelines</a>.</li>
+href="//www.w3.org/TR/xhtml1/">XHTML-1.0 guidelines</a>.</li>
 
 <li>Our server-side includes declare UTF-8 as the character encoding, so
 using any other encoding is problematic.</li>
 </ul>
 
 
-<h3 id="styling">9. Styling</h3>
+<h3 id="styling">Styling</h3>
 
 
 <h4>Styling of templated pages</h4>
 
 <ul>
 <li>Generic styling for desktops and smartphones is provided by
-<code>layout.css</code>, which contains gnu.org-specific formatting, and
-defines a few responsive classes that cover most of our use cases. This
-stylesheet also includes some &ldquo;reset&rdquo; definitions from the <a
-href="https://web.archive.org/web/20070930230754/http://developer.yahoo.com:80/yui/";>
-YUI library, version&nbsp;2</a>), to normalize the default rendering of
-HTML elements that are not otherwise redefined.</li>
+<code>/layout.css</code>; it covers most of our use cases.</li>
 
 <li>Mobile devices with very limited resources use <code>/mini.css</code>.
 This stylesheet is just the YUI (version&nbsp;2) reset and base stylesheets,
@@ -452,14 +430,6 @@
 background could end up the same.  Please use a stylesheet for
 this, and not HTML 3.2 (HTML 4 Transitional) deprecated
 markup.</li>
-
-<li><em>Note about grids:</em>&nbsp; Very few pages currently use them.  In the
-event you'd like to create one that does, good starting points may be
-found in <a
-href="https://web.archive.org/web/20190917161357/http://yuilibrary.com/yui/docs/cssgrids/";>
-YUI version&nbsp;3</a>, and <a
-href="https://purecss.io/grids/";>Pure Grids</a>. The components provided by
-these libraries are licensed under the modified (3-clause) BSD license.</li>
 </ul>
 
 
@@ -488,7 +458,7 @@
 </ul>
 
 
-<h3 id="UseofGraphics">10. Use of Graphics</h3>
+<h3 id="UseofGraphics">Use of Graphics</h3>
 
 
 <ul>
@@ -519,7 +489,7 @@
 <li>Always have a textual alternative for in-line images, to ensure
 indexability by search engines and accessibility.  For instance:
 <p class="emph-box"><code>&lt;img src="/graphics/*.jpg"
-title="[BRIEF TEXT]" alt="&amp;nbsp;[DESCRIPTIVE 
TEXT]&amp;nbsp;"&gt;</code></p>
+alt="&amp;nbsp;[DESCRIPTIVE TEXT]&amp;nbsp;"&gt;</code></p>
 We add the non-breaking spaces (&amp;nbsp;) and square brackets to
 separate the DESCRIPTIVE TEXT from adjacent text, and help the user
 realize that this is a stand-in for an image.  The point of using
@@ -531,15 +501,15 @@
 when displayed at its original size, using the browser's default font
 size.</li>
 
-<li>Adjust image width or height in a style attribute, using scalable
-units such as <code>em</code> or <code>%</code>; for instance:
+<li><p>Adjust image width or height in a style attribute, using scalable
+units such as <code>em</code> or <code>%</code>; for instance:</p>
+
 <p class="emph-box"><code>&lt;img src="/graphics/*.jpg"
 alt="&amp;nbsp;[DESCRIPTIVE TEXT]&amp;nbsp;"
-style="width: 10em; height: auto;" width="77px" height="77px" /&gt;</code></p>
-This way, the page will look the same if the reader increases or
-decreases font size.<br>Specifying both <code>width</code> and
-<code>height</code> will reserve the space required for the image during
-the page loading phase.</li>
+style="width: 10em; height: auto;" /&gt;</code></p>
+
+<p>This way, the page will look the same if the reader increases or
+decreases font size.</p></li>
 
 <li>If you are adding a small floating image to a page that uses
 <code>layout.css</code> (the stylesheet for <a
@@ -556,7 +526,7 @@
 attribute if none of the predefined ones fits your needs); for instance:
 
 <p class="emph-box"><code>&lt;div class="pict wide"
-style="width: 25em;"&gt;&lt;img src="/graphics/*.jpg"
+style="width: 25em"&gt;&lt;img src="/graphics/*.jpg"
 alt="&amp;nbsp;[DESCRIPTIVE TEXT]&amp;nbsp;"
 /&gt;&lt;/div&gt;</code></p>
 
@@ -570,22 +540,17 @@
 <p class="imgleft">
 <a href="/graphics/agnuhead.html"><img
    src="/graphics/gnu-head-sm.jpg"
-   title="Head of a GNU"
-   alt="&nbsp;[Black and white sketch of the Head of a GNU]&nbsp;"
-   style="width: 8em; height: auto"
-   width="129px" height="122px" />
+   alt="&nbsp;[Image of the Head of a GNU]&nbsp;"
+   style="width: 8em" />
 </a></p>
 
 <pre class="emph-box">
 &lt;p class="imgleft"&gt;
-  &lt;a href="/graphics/agnuhead.html"&gt;
-    &lt;img src="/graphics/gnu-head-sm.jpg"
-          title="Head of a GNU"
-          alt="&nbsp;[Black and white sketch of the Head of a GNU]&nbsp;"
-          style="width: 8em; height: auto"
-          width="129px" height="122px" /&gt;
-  &lt;/a&gt;
-&lt;/p&gt;
+&lt;a href="/graphics/agnuhead.html"&gt;
+&lt;img src="/graphics/gnu-head-sm.jpg"
+     alt="&nbsp;[Image of the Head of a GNU]&nbsp;"
+     style="width: 8em" /&gt;
+&lt;/a&gt;&lt;/p&gt;
 </pre>
 <div style="clear: both"></div>
 
@@ -594,7 +559,7 @@
 </ul>
 
 
-<h3 id="pollinking">11. Appendix 1 - Linking Policies</h3>
+<h3 id="pollinking">Appendix 1 - Linking Policies</h3>
 
 
 <p>One of the most complex aspects of maintaining web pages is following the
@@ -678,9 +643,9 @@
 well-known proprietary software.  For example, the following
 text&mdash;and not much else&mdash;would be acceptable:</p>
 
-<blockquote>w3 is a web browser for GNU Emacs, similar to Internet Explorer.
+<blockquote><p>w3 is a web browser for GNU Emacs, similar to Internet Explorer.
 It can run on all platforms GNU Emacs runs on, including GNU/Linux,
-proprietary Unix systems, and Windows.</blockquote>
+proprietary Unix systems, and Windows.</p></blockquote>
 
 <p>Links which appear in other areas, such as the testimonials or
 philosophy pages, as well as links to user groups may discuss such
@@ -698,8 +663,8 @@
 project pages should have little mention of open source.  The GNOME
 page used to provide a good example of a tactful way to do it:</p>
 
-<blockquote>GNOME is part of the GNU Project, and is free software (sometimes
-referred to as open source software).</blockquote>
+<blockquote><p>GNOME is part of the GNU Project, and is free software 
(sometimes
+referred to as open source software).</p></blockquote>
 
 <p>Any exceptions to this rule should be apparent from the context.
 For instance, user groups pages may talk in greater detail about
@@ -751,25 +716,24 @@
 </dl>
 
 
-<h3 id="repo">12. Appendix 2 - Working with Web CVS Repositories</h3>
+<h3 id="repo">Appendix 2 - Working with Web CVS Repositories</h3>
 
 
 <h4 id="cvs">Basic CVS commands</h4>
 
 <ul>
+<li>For reference manual, execute <kbd>info cvs</kbd>.</li>
+
 <li>
 Before the initial checkout, set the environment variable
-<code>CVS_RSH=ssh</code>.<br>In alternative, on Debian-like systems you can
-replace <code>:ext:</code> with
-<a href="/software/trans-coord/manual/cvs/cvs.html#Connecting-with-rsh-or-ssh">
-  <code>:extssh:</code></a> in each command.</li>
+<code>CVS_RSH=ssh</code>.</li>
 
 <li>
 <p>If you have write access to www, check out the main www repository
 with your Savannah login:</p>
 
 <pre class="emph-box">
-cvs -z3 -d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/www co www
+<kbd>cvs -z3 -d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/www co 
www</kbd>
 </pre>
 
 <p>You will get a working directory, <code>www</code>, with the same
@@ -781,20 +745,21 @@
 anonymous checkout of www:</p>
 
 <pre class="emph-box">
-cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/web/www co www
+<kbd>cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/web/www co www</kbd>
 </pre>
 </li>
 
 <li>
-<p>Check out the web repository of the fooproject:</p>
+<p>Check out the web repository of the <var>fooproject</var>:</p>
 
 <pre class="emph-box">
-cvs -z3 
-d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/<var>fooproject</var> co 
<var>fooproject</var>
+<kbd>cvs -z3 
-d:ext:<var>username</var>@cvs.savannah.gnu.org:/web/<var>fooproject</var> \
+         co <var>fooproject</var></kbd>
 </pre>
 
-<p>You will get a working directory, <code>fooproject</code>, with the same
-structure as the <code>www/software/fooproject</code> subdirectory.  Note,
-however, that the fooproject and www repositories are independent.  The
+<p>You will get a working directory, <code><var>fooproject</var></code>, with 
the same
+structure as the <code>www/software/<var>fooproject</var></code> subdirectory. 
 Note,
+however, that the <var>fooproject</var> and www repositories are independent.  
The
 working directories can be anywhere in your filesystem.</p>
 
 <p><em>Webmasters, please read <a
@@ -807,7 +772,7 @@
 <p>Add a file or directory:</p>
 
 <pre class="emph-box">
-cvs add foo
+<kbd>cvs add <var>foo</var></kbd>
 </pre>
 </li>
 
@@ -815,7 +780,7 @@
 <p>Update before you edit a file:</p>
 
 <pre class="emph-box">
-cvs update -P foo
+<kbd>cvs update -P <var>foo</var></kbd>
 </pre>
 </li>
 
@@ -823,7 +788,7 @@
 <p>Check the changes you are going to commit:</p>
 
 <pre class="emph-box">
-cvs diff -U2 foo
+<kbd>cvs diff -U2 <var>foo</var></kbd>
 </pre>
 </li>
 
@@ -832,7 +797,7 @@
 already in the repository):</p>
 
 <pre class="emph-box">
-cvs commit foo
+<kbd>cvs commit <var>foo</var></kbd>
 </pre>
 
 <p>This will open a text editor where you should enter a log message.  The
@@ -912,8 +877,9 @@
 href="#NamingTranslations">naming
 conventions</a>.  This makes it impossible to use
 symlinks to redirect to and from HTML files whose names look like
-translations, that is, <code>page.<var>ll</var>.html</code> or
-<code>page.<var>ll-cc</var>.html</code>, where ll and cc are two-letter
+translations, that is, <code><var>page</var>.<var>ll</var>.html</code> or
+<code><var>page</var>.<var>ll</var>-<var>cc</var>.html</code>, where
+<var>ll</var> and <var>cc</var> are two-letter
 codes.  When you need such redirections, use the <a
 href="#htaccess">htaccess mechanism</a>.</p>
 
@@ -929,13 +895,12 @@
 redirection in some cases.  You can do this either in the top-level
 control file <code>.htaccess</code>, or by using something like this as the
 file to be redirected:</p>
+
 <p class="emph-box"><code>
 &lt;meta http-equiv="refresh" content="0;
   url=https://www.gnu.org/<var>target</var>"&gt;
 </code></p>
-However, the latter must be implemented so as
-<a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F41";
-rel="noopener">WCAG 2.1 F41</a> does not occur in any circumstance.
+
 
 <h4 id="scripts">Server-side scripts</h4>
 
@@ -952,44 +917,26 @@
 unless you have a specific reason to do so.</p>
 
 
-<h3 id="UsefulResources">13. Useful Resources</h3>
+<h3 id="UsefulResources">Useful Resources</h3>
 
 
 <ul>
 <li>Outside gnu.org:
   <ul>
     <li>We follow the guidelines of the <a
-    href="https://www.anybrowser.org/campaign/"; rel="noopener"
-    style="text-decoration: none;">
-      <img src="../graphics/icons/anybrowser.png" width="96px" height="18px"
-      title="Visit the 'Best Viewed on Any Browser' campaign website"
-      alt="Best Viewed on Any Browser"
-      style="vertical-align: middle" /></a>
-      campaign.</li>
-
-    <!-- Removed on 01/2021; superseded by HTML 5 (W3C Recommendation).
-    <li>Use of the <a
-    href="https://www.cs.tcd.ie/15445/UG.HTML";>ISO</a> standard for the
-    <a href="https://www.w3.org/MarkUp/";>Hypertext Markup Language
-    (HTML)</a> allows for consistent backwards compatibility among web
-    user agents.</li>-->
+    href="//www.anybrowser.org/campaign/">Best Viewed with Any
+    Browser</a> campaign.</li>
+
+    <li>Basic info on the web and its technical specifications can be
+    found at <a href="//www.w3.org/">The World Wide Web
+    Consortium</a>.</li>
 
-    <!-- Removed on 01/2021 because of declared obsolescence.
     <li>The GNU web server follows the w3.org <a
-    href="https://www.w3.org/Provider/Style/Overview.html";>Style
-    Guide</a>.</li>-->
+    href="//www.w3.org/Provider/Style/Overview.html">Style
+    Guide</a>.</li>
 
-    <li>Use of <a href="https://w3.org/TR/2021/SPSD-html52-20210128/";
-    rel="noopener">HTML&nbsp;5.2</a> allows for consistent backwards
-    compatibility among web browsers.</li>
-
-    <li>Use of <a href="https://www.w3.org/TR/2020/NOTE-css-2020-20201222/";
-    rel="noopener">CSS3 RECs</a> in place of WDs and CRs allows for stable
-    cross-browser styling.</li>
-
-    <li>Use of <a href="https://www.w3.org/TR/2018/REC-WCAG21-20180605/";
-    rel="noopener">WCAG&nbsp;2.1</a> ensures accessibility for a wide range of
-    people with disabilities.</li>
+    <li>Use of <a href="//w3.org/TR/WCAG21/">WCAG 2.1</a> helps
+    ensure accessibility for a wide range of people with disabilities.</li>
   </ul>
 </li>
 
@@ -997,10 +944,6 @@
   <ul>
     <li><a href="#content">The GNU Website Guidelines</a> (this page);</li>
 
-    <li>The
-    <a href="/software/trans-coord/manual/cvs/">reference manual</a> of our CVS
-    (also offline by executing <kbd>info cvs</kbd>);</li>
-
     <li>Guidelines for
     <a href="/server/standards/README.editors.html">Web Page Creation</a> at
     www.gnu.org;</li>
@@ -1022,7 +965,7 @@
     <li><a 
href="/software/trans-coord/manual/gnun/html_node/Webmaster-Tips.html">
     Tips for webmasters</a> to make translators' job easier;</li>
 
-    <li><a 
href="https://savannah.gnu.org/maintenance/FrontPage/";>Documentation for
+    <li><a href="//savannah.gnu.org/maintenance/FrontPage/">Documentation for
     Savannah</a>, the SourceForge clone dedicated to the GNU Project;</li>
 
     <li><a href="/prep/gnumaint/README">
@@ -1095,7 +1038,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/02/10 13:26:50 $
+$Date: 2021/02/11 12:08:01 $
 <!-- timestamp end --></p>
 </div>
 </div><!-- for class="inner", starts in the banner include -->