[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards gnu-website-guidelines.html
|
From: |
Therese Godefroy |
|
Subject: |
www/server/standards gnu-website-guidelines.html |
|
Date: |
Mon, 15 Feb 2021 07:27:41 -0500 (EST) |
CVSROOT: /webcvs/www
Module name: www
Changes by: Therese Godefroy <th_g> 21/02/15 07:27:41
Modified files:
server/standards: gnu-website-guidelines.html
Log message:
Update and improve (www-discuss 2021-02-13).
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.18&r2=1.19
Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /webcvs/www/www/server/standards/gnu-website-guidelines.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- gnu-website-guidelines.html 24 Jan 2021 07:55:22 -0000 1.18
+++ gnu-website-guidelines.html 15 Feb 2021 12:27:40 -0000 1.19
@@ -1,25 +1,17 @@
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.86 -->
+<!-- Parent-Version: 1.95 -->
<title>Website Guidelines - GNU Project - Free Software Foundation</title>
-<style type="text/css" media="print,screen"><!--
-ul li { margin-top: 1em; }
---></style>
<!--#include virtual="/server/standards/po/gnu-website-guidelines.translist"
-->
<!--#include virtual="/server/banner.html" -->
<h2>GNU Website Guidelines</h2>
-<p>Our goal is to get information to people. Keeping the site
-design simple helps accomplish that.</p>
-
-<p>Please be considerate of all who access our web pages, and accommodate
-them, including those who use text-only browsers or old browsers, as well
-as those with slow connections. We wish to prevent HTML design that looks
-great under one version of one browser, and ugly under many others. Of
-course, please don't install any of the proprietary software browsers
-available if you don't already use them anyway.</p>
-
+<p class="center emph-box">
+ Our goal is to get information to people.
+ Keeping the site design simple helps accomplish that.
+</p>
<div class="summary">
+<hr class="no-display" />
<h3 class="no-display">Table of Contents</h3>
<ul>
<li><a href="#GeneralGuidelines">General Guidelines</a></li>
@@ -44,14 +36,21 @@
</li>
<li><a href="#UsefulResources">Useful Resources</a></li>
</ul>
-</div>
<hr class="no-display" />
+</div>
+<p>Please be considerate of all who access our web pages, and accommodate
+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">General Guidelines</h3>
+<h3 id="GeneralGuidelines" class="subheader">General Guidelines</h3>
-<ul>
+
+<ul class="para">
<li>The GNU web server has only <a href="/philosophy/free-sw.html">free
software</a> available. We prefer that only free software be used to
prepare pages for the GNU web server.</li>
@@ -107,10 +106,10 @@
</ul>
-<h3 id="CopyrightGuidelines">Copyright Guidelines</h3>
+<h3 id="CopyrightGuidelines" class="subheader">Copyright Guidelines</h3>
-<ul>
+<ul class="para">
<li>Every page should have a copyright notice. See the <a
href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&content-type=text%2Fplain">
boilerplate</a>, referred below.</li>
@@ -151,10 +150,10 @@
</ul>
-<h3 id="orthography">Spelling and Punctuation</h3>
+<h3 id="orthography" class="subheader">Spelling and Punctuation</h3>
-<ul>
+<ul class="para">
<li>English pages should follow the standard American spelling,
hyphenation and punctuation conventions.</li>
@@ -162,12 +161,13 @@
regards hyphenation and quotes, gnu.org adds its own rules for the sake of
consistency:
<ul>
- <li>“Nonfree” is preferred over “non-free”;
+ <li>The term “nonfree” is preferred over “non-free”;
likewise, “noncommercial” over “non-commercial.”</li>
<li>In ordinary text, HTML entities
- “&ldquo;...&rdquo;” and
- “&lsquo;...&rsquo;” are preferred over straight quotes
- ("..." and '...'). This doesn't apply to script-generated documents.</li>
+ “<code>&ldquo;</code>…<code>&rdquo;</code>” and
+ “<code>&lsquo;</code>…<code>&rsquo;</code>”
+ are preferred over straight quotes ("..." and '...').
+ This doesn't apply to script-generated documents.</li>
<li>Where they exist, the double spaces after sentence breaks should be
preserved. They enable Emacs sentence commands to do the right thing.</li>
</ul>
@@ -176,12 +176,12 @@
<a id="FilenameAndURLGuidelines"></a>
-<h3 id="filenames">Filenames</h3>
+<h3 id="filenames" class="subheader">Filenames</h3>
-<ul>
+<ul class="para">
<li>To make simultaneous edition of many files easier,
-try and give each HTML file a unique name; the filename
+try and give each HTML file a unique and descriptive name; the special filename
<code>index.html</code> should only be used as a symbolic link, as
explained next.</li>
@@ -192,21 +192,21 @@
file to handle this.</li>
<li id="NamingTranslations">If you translate your web page in different
-languages, please name the English file <code>ARTICLE.html</code>, and
-its translations <code>ARTICLE.LANG.html</code>. LANG should contain the
-two-letter language code from <a
-href="https://www.loc.gov/standards/iso639-2/php/code_list.php";>ISO 639</a>,
+languages, please name the English file <code><var>article</var>.html</code>,
and
+its translations <code><var>article</var>.<var>lang</var>.html</code>—
+<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>
+ISO 3166 (lowercase). 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">URLs</h3>
+<h3 id="urls" class="subheader">URLs</h3>
-<ul>
+<ul class="para">
<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>
@@ -216,6 +216,9 @@
<code>http://www.gnu.org/</code> will be wrong when the visitor uses
HTTPS.</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
file in the same directory. These relative links are to be
@@ -232,20 +235,12 @@
as things get moved around.</li>
<li>Be sure to omit the filename entirely when linking to an anchor in
-the same file.</li>
+the same file and double-check that the anchor actually works.</li>
<li>Consider others linking to your page when removing an anchor or
<code>id</code> attribute.</li>
-<li>Cite FTP locations of source code with the full URL of the
-directory they are in:
-<p class="emph-box"><code>
-<a
href="https://ftp.gnu.org/gnu/foo">https://ftp.gnu.org/gnu/foo</a>
-</code></p>
-which browsers display this way:<br />
-<a href="https://ftp.gnu.org/gnu/";>https://ftp.gnu.org/gnu/foo</a><br />
-
-We encourage FTP sites to use a directory for each package, and only put
+<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
versions of that package and related information can be downloaded
(e.g., a <code>README</code> file, information of what versions are
@@ -253,22 +248,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 this way:
+<li><p>Cite people with e-mail addresses this way:</p>
<p class="emph-box"><code>
-<a href="https://www.stallman.org/">Richard Stallman</a>
+<a href="//www.stallman.org/">Richard Stallman</a>
<a href="mailto:rms@gnu.org">&lt;rms@gnu.org&gt;</a>
</code></p>
-which browsers display this way:<br />
-<a href="https://www.stallman.org/";>Richard Stallman</a>
-<a href="mailto:rms@gnu.org";><rms@gnu.org></a><br />
-It is less confusing to the user, because it's clear what is a
-<code>http(s):</code> link to another web page and what is a
-<code>mailto:</code> anchor that
+<p>which browsers display this way:</p>
+<p class="emph-box" style="background-color: inherit">
+<a href="//www.stallman.org/">Richard Stallman</a>
+<a href="mailto:rms@gnu.org";><rms@gnu.org></a>
+</p>
+<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
@@ -283,20 +279,20 @@
</ul>
-<h3 id="HTMLGuidelines">HTML Guidelines</h3>
+<h3 id="HTMLGuidelines" class="subheader">HTML Guidelines</h3>
-<ul>
+<ul class="para">
<li>HTML on the GNU web server should be strictly compliant with
-<a href="https://www.w3.org/standards/";>W3C standards</a>.</li>
+<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
-elements</a> such as <html> <head> <title>
-<body>, etc. when using (X)HTML, and always include the
-appropriate DTD or Schema reference. This appeases overly pedantic
-browsers.</li>
+href="//www.w3.org/TR/html401/struct/global.html#h-7.1">required
+elements</a> such as <code><html></code>, <code><head></code>,
+<code><title></code>, <code><body></code>, etc. when using (X)HTML,
+and always include the appropriate DTD or Schema reference.
+This appeases overly pedantic web browsers.</li>
<li>Do not add comments at the top of a document. Web browsers
expect the doctype, XML declaration, or Schema to be at the top.
@@ -305,7 +301,7 @@
<li>The <head> element should contain this line:
<p class="emph-box">
-<code><link rev="made" href="mailto:webmasters@gnu.org"></code></p>
+<code><link rel="author" href="mailto:webmasters@gnu.org"></code></p>
Some browsers use this information to allow users to easily report
problems they find on a page.</li>
@@ -326,7 +322,7 @@
<li>Acronyms/abbreviations:
<ul>
- <li>Never use <code><acronym></code>: HTML5 obsoletes it in
+ <li>Never use <code><acronym></code>: HTML 5 obsoletes it in
favor of <code><abbr></code>.</li>
<li>Don't use <code><abbr></code> unless for a really
@@ -349,10 +345,10 @@
</ul>
-<h3 id="tables">Tables and menus</h3>
+<h3 id="tables" class="subheader">Tables and menus</h3>
-<ul>
+<ul class="para">
<li>Please use tables to organize data, not the presentation of the
web page.</li>
@@ -360,7 +356,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
@@ -378,10 +374,10 @@
</ul>
-<h3 id="templating">Using our page template</h3>
+<h3 id="templating" class="subheader">Using our page template</h3>
-<ul>
+<ul class="para">
<li>To help people follow the above guidelines, a page template (or
“boilerplate”) is provided for both the main part of the GNU
website, and the software projects. Its use is mandatory for new pages in
@@ -391,36 +387,35 @@
original source</a> of the boilerplate instead, and follow the instructions
in it.</li>
-<li>The templated pages must follow the <a
-href="https://www.w3.org/TR/xhtml1/";>XHTML-1.0 guidelines</a>.</li>
+<li>The XHTML templated pages must follow the <a
+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">Styling</h3>
+<h3 id="styling" class="subheader">Styling</h3>
<h4>Styling of templated pages</h4>
-<ul>
-<li>Generic styling for desktops and smartphones is provided by two CSS:
-<code>/reset.css</code> (from the <a
-href="//web.archive.org/web/20070930230754/http://developer.yahoo.com:80/yui/";>
-YUI library, version 2</a>), which normalizes the default rendering of all
-HTML elements by the various browsers, and <code>/layout.css</code>, which
-contains gnu.org-specific formatting. A few responsive elements are defined
-in <code>/layout.css</code>. They cover most of our use cases.</li>
+<ul class="para">
+<li>Generic styling for desktops and smartphones is provided by
+<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 2) reset and base stylesheets,
as these
-devices typically have minimal need for various fonts and no need for
-fancy layouts.</li>
+This stylesheet is just the YUI (version 2) reset and base stylesheets,
+as these devices typically have minimal need for various fonts and no need
+for fancy layouts.</li>
<li>Printers use <code>/print.css</code>. Note that the header, navigation
bars and footer (except copyright and license) are unprintable.</li>
+<li>In addition to <code>/layout.css</code>, some pages have specialized
+stylesheets: <code>/graphics/graphics.css</code> for the GNU Art section,
+and <code>/side-menu.css</code> for the Malware and Education sections.</li>
+
<li>If some special styling is needed for a specific page, it should be added
to the page itself in a <style> element, between the SSI directives
that include <code>header.html</code> and <code>banner.html</code>. If the
@@ -434,37 +429,38 @@
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> 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="//web.archive.org/web/20190917161357/http://yuilibrary.com/yui/docs/cssgrids/";>
-YUI version 3</a>, and <a
-href="//purecss.io/grids/">Pure Grids</a>. The components provided by
-these libraries are licensed under the modified (3-clause) BSD license.</li>
</ul>
<h4>Other stylesheets</h4>
-<ul>
+<ul class="para">
<li>Historical pages (unmaintained translations for the most part) refer
to <code>/gnu.css</code>, which in turn loads <code>/mini.css</code>,
as these pages are
usually very basic, plain pages with little or no formatting.</li>
-<li>Some software manuals use a dedicated CSS, <code>/style.css</code>.</li>
+<li>There are dedicated stylesheets for software manuals. The main ones are:
+ <ul>
+ <li><code>/style.css</code>;</li>
+ <li><a href="/software/gnulib/manual.css">gnulib.css</a>,
+ which imports <code>/style.css</code> and adds a few more definitions;
+ it is used by <code>gendocs.sh</code> to <a
+ href="/prep/maintain/html_node/Invoking-gendocs_002esh.html">
+ regenerate Texinfo manuals</a>.</li>
+ </ul>
+</li>
-<li>Translators maintain stylesheets (<code>/style.LANG.css</code>) that
+<li>Translators maintain stylesheets (<code>/style.<var>lang</var>.css</code>)
that
modify layout.css according to their own needs. The RTL languages (Arabic,
Persian, and Hebrew) use <code>/style.rtl.css</code>.</li>
</ul>
-<h3 id="UseofGraphics">Use of Graphics</h3>
+<h3 id="UseofGraphics" class="subheader">Use of Graphics</h3>
-<ul>
+<ul class="para">
<li>The use of graphics should be minimized, so pages load fast
over slow links, especially animations.</li>
@@ -489,8 +485,8 @@
<li>Before you take an image from another website, please ask for
permission to use it.</li>
-<li>Always have a textual alternative for in-line images, for people
-who have text-only access to the web. For instance:
+<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><img src="/graphics/*.jpg"
alt="&nbsp;[DESCRIPTIVE TEXT]&nbsp;"></code></p>
We add the non-breaking spaces (&nbsp;) and square brackets to
@@ -504,13 +500,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><img src="/graphics/*.jpg"
alt="&nbsp;[DESCRIPTIVE TEXT]&nbsp;"
-style="width: 10em" /></code></p>
-This way, the page will look the same if the reader increases or
-decreases font size.</li>
+style="width: 10em; height: auto;" /></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
@@ -542,16 +540,16 @@
<a href="/graphics/agnuhead.html"><img
src="/graphics/gnu-head-sm.jpg"
alt=" [Image of the Head of a GNU] "
- style="width: 8em" />
-</a></p>
+ style="width: 8em" /></a>
+</p>
<pre class="emph-box">
<p class="imgleft">
<a href="/graphics/agnuhead.html">
<img src="/graphics/gnu-head-sm.jpg"
alt=" [Image of the Head of a GNU] "
- style="width: 8em" />
-</a></p>
+ style="width: 8em" /></a>
+</p>
</pre>
<div style="clear: both"></div>
@@ -560,7 +558,7 @@
</ul>
-<h3 id="pollinking">Appendix 1 - Linking Policies</h3>
+<h3 id="pollinking" class="subheader">Appendix 1 - Linking Policies</h3>
<p>One of the most complex aspects of maintaining web pages is following the
@@ -717,12 +715,14 @@
</dl>
-<h3 id="repo">Appendix 2 - Working with Web CVS Repositories</h3>
+<h3 id="repo" class="subheader">Appendix 2 - Working with Web CVS
Repositories</h3>
<h4 id="cvs">Basic CVS commands</h4>
-<ul>
+<ul class="para">
+<li>For reference manual, execute <kbd>info cvs</kbd>.</li>
+
<li>
Before the initial checkout, set the environment variable
<code>CVS_RSH=ssh</code>.</li>
@@ -732,7 +732,7 @@
with your Savannah login:</p>
<pre class="emph-box">
-cvs -z3 -d:ext:<username>@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
@@ -744,20 +744,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:<username>@cvs.savannah.gnu.org:/web/fooproject co
fooproject
+<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
@@ -770,7 +771,7 @@
<p>Add a file or directory:</p>
<pre class="emph-box">
-cvs add foo
+<kbd>cvs add <var>foo</var></kbd>
</pre>
</li>
@@ -778,7 +779,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>
@@ -786,7 +787,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>
@@ -795,7 +796,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
@@ -860,12 +861,12 @@
<p>On each line the first file name must be a relative path name to an
existing file. The second file name may not contain any slash; it is the
name of the symbolic link to be created in the present directory. For
-instance, if a page named <code>DIR.html</code> exists in the
-<code>/DIR</code> directory, and <code>index.html</code> does not exist,
-<code>/DIR/.symlinks</code> should contain a line like this:</p>
+instance, if a page named <code><var>dir</var>.html</code> exists in the
+<code>/<var>dir</var></code> directory, and <code>index.html</code> does not
exist,
+<code>/<var>dir</var>/.symlinks</code> should contain a line like this:</p>
<pre class="emph-box">
-DIR.html index.html
+<var>dir</var>.html index.html
</pre>
<p>The <code>ln -s</code> analogy accounts for only part of the story.
@@ -875,8 +876,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>
@@ -895,11 +897,11 @@
<p class="emph-box"><code>
<meta http-equiv="refresh" content="0;
- url=http://www.gnu.org/target">
+ url=https://www.gnu.org/<var>target</var>">
</code></p>
-<h4 id="scripts">Scripts</h4>
+<h4 id="scripts">Server-side scripts</h4>
<p>A <a href="/server/source/source.html">description of scripts and
software</a> used on www.gnu.org is available. Please read it before
@@ -914,35 +916,32 @@
unless you have a specific reason to do so.</p>
-<h3 id="UsefulResources">Useful Resources</h3>
+<h3 id="UsefulResources" class="subheader">Useful Resources</h3>
-<ul>
+<ul class="para">
<li>Outside gnu.org:
<ul>
<li>We follow the guidelines of the <a
- href="https://www.anybrowser.org/campaign/";>Best Viewed with Any
+ 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="https://www.w3.org/";>The World Wide Web
+ found at <a href="//www.w3.org/">The World Wide Web
Consortium</a>.</li>
- <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>
-
<li>The GNU web server follows the w3.org <a
- href="https://www.w3.org/Provider/Style/Overview.html";>Style
+ href="//www.w3.org/Provider/Style/Overview.html">Style
Guide</a>.</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>
<li>On gnu.org:
<ul>
- <li><a href="#content">The GNU Website Guidelines</a>;</li>
+ <li><a href="#content">The GNU Website Guidelines</a> (this page);</li>
<li>Guidelines for
<a href="/server/standards/README.editors.html">Web Page Creation</a> at
@@ -956,7 +955,7 @@
Statement</a>;</li>
<li><a href="/server/standards/README.webmastering.html">GNU
- Webmastering Guidelines;</a></li>
+ Webmastering Guidelines</a>;</li>
<li>Guide to
<a href="/server/standards/README.translations.html">translating</a> GNU
@@ -972,9 +971,9 @@
README</a> for the <code>/prep/gnumaint/</code> directory (those files
are primarily used by <a href="/prep/maintain/">GNU maintainer
administrators</a>, and occasionally by GNU webmasters, to update
- the <code>/*/allgnupkgs.html</code> files in www).</li>
+ the <code>/*/allgnupkgs.html</code> files in www);</li>
- <li>Here is the <a href="/server/tasks.html">help</a> we need with our
+ <li><a href="/server/tasks.html">How to help</a> with our
<a href="/server/server.html">web server</a>.</li>
</ul>
</li>
@@ -1000,13 +999,13 @@
to <a href="mailto:web-translators@gnu.org";>
<web-translators@gnu.org></a>.</p>
- <p>For information on coordinating and submitting translations of
+ <p>For information on coordinating and contributing translations of
our web pages, see <a
href="/server/standards/README.translations.html">Translations
README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting translations
+README</a> for information on coordinating and contributing translations
of this article.</p>
</div>
@@ -1027,7 +1026,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2010, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021
Free Software
+<p>Copyright © 2010, 2013-2021 Free Software
Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
@@ -1038,7 +1037,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2021/01/24 07:55:22 $
+$Date: 2021/02/15 12:27:40 $
<!-- timestamp end --></p>
</div>
</div><!-- for class="inner", starts in the banner include -->
- www/server/standards gnu-website-guidelines.html,
Therese Godefroy <=