[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards gnu-website-guidelines.html
|
From: |
Lorenzo L. Ancora |
|
Subject: |
www/server/standards gnu-website-guidelines.html |
|
Date: |
Mon, 26 Apr 2021 10:31:05 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: Lorenzo L. Ancora <lorenzoancora> 21/04/26 10:31:05
Modified files:
server/standards: gnu-website-guidelines.html
Log message:
Fix. ending tag mismatch.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/gnu-website-guidelines.html?cvsroot=www&r1=1.30&r2=1.31
Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /web/www/www/server/standards/gnu-website-guidelines.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- gnu-website-guidelines.html 26 Apr 2021 14:22:15 -0000 1.30
+++ gnu-website-guidelines.html 26 Apr 2021 14:31:05 -0000 1.31
@@ -78,54 +78,54 @@
<ul class="columns">
<li><p><a href="#GeneralGuidelines"><b>General Guidelines</b></a>
<ul>
- <li><p><a href="#gnu-policies">GNU policies</a><p></li>
- <li><p><a href="#CopyrightGuidelines">Copyright guidelines</a><p></li>
- <li><p><a href="#HTMLGuidelines">Web and Accessibility
Standards</a><p></li>
- </ul><p></li>
+ <li><p><a href="#gnu-policies">GNU policies</a></p></li>
+ <li><p><a href="#CopyrightGuidelines">Copyright guidelines</a></p></li>
+ <li><p><a href="#HTMLGuidelines">Web and Accessibility
Standards</a></p></li>
+ </ul></p></li>
<li><p><a href="#new-page"><b>Creating a New Page</b></a>
<ul>
- <li><p><a href="#filenames">Naming the file</a><p></li>
- <li><p><a href="#html-required">Doctype and required HTML
elements</a><p></li>
- <li><p><a href="#page-footer">Page footer</a><p></li>
- <li><p><a href="#templating">Using our page template</a><p></li>
- </ul><p></li>
+ <li><p><a href="#filenames">Naming the file</a></p></li>
+ <li><p><a href="#html-required">Doctype and required HTML
elements</a></p></li>
+ <li><p><a href="#page-footer">Page footer</a></p></li>
+ <li><p><a href="#templating">Using our page template</a></p></li>
+ </ul></p></li>
<li><p><a href="#writing"><b>Writing and Editing</b></a>
<ul style="display: inline-block">
- <li><p><a href="#page-contents">Page contents</a><p></li>
- <li><p><a href="#orthography">Spelling and punctuation</a><p></li>
- <li><p><a href="#urls">URLs - local links</a><p></li>
- <li><p><a href="#anchors">URLs - page anchors</a><p></li>
- <li><p><a href="#external-links">URLs - external links</a><p></li>
- <li><p><a href="#mailto">URLs - email links</a><p></li>
- <li><p><a href="#abbreviations">Acronyms and abbreviations</a><p></li>
- <li><p><a href="#tables">Tables and menus</a><p></li>
- </ul><p></li>
+ <li><p><a href="#page-contents">Page contents</a></p></li>
+ <li><p><a href="#orthography">Spelling and punctuation</a></p></li>
+ <li><p><a href="#urls">URLs - local links</a></p></li>
+ <li><p><a href="#anchors">URLs - page anchors</a></p></li>
+ <li><p><a href="#external-links">URLs - external links</a></p></li>
+ <li><p><a href="#mailto">URLs - email links</a></p></li>
+ <li><p><a href="#abbreviations">Acronyms and abbreviations</a></p></li>
+ <li><p><a href="#tables">Tables and menus</a></p></li>
+ </ul></p></li>
<li><p><a href="#styling"><b>Styling</b></a>
<ul>
- <li><p><a href="#styling-templated">Styling of templated
pages</a><p></li>
- <li><p><a href="#other-stylesheets">Other stylesheets</a><p></li>
- <li><p><a href="#text-only">Text-only browsers</a><p></li>
- </ul><p></li>
+ <li><p><a href="#styling-templated">Styling of templated
pages</a></p></li>
+ <li><p><a href="#other-stylesheets">Other stylesheets</a></p></li>
+ <li><p><a href="#text-only">Text-only browsers</a></p></li>
+ </ul></p></li>
<li><p><a href="#UseofGraphics"><b>Use of Graphics</b></a>
<ul>
- <li><p><a href="#caveats">Caveats</a><p></li>
- <li><p><a href="#image-basics">Basic recommendations</a><p></li>
- <li><p><a href="#image-css">CSS classes for images</a><p></li>
- </ul><p></li>
- <li><p><a href="#pollinking"><b>Linking Criteria</b></a><p></li>
+ <li><p><a href="#caveats">Caveats</a></p></li>
+ <li><p><a href="#image-basics">Basic recommendations</a></p></li>
+ <li><p><a href="#image-css">CSS classes for images</a></p></li>
+ </ul></p></li>
+ <li><p><a href="#pollinking"><b>Linking Criteria</b></a></p></li>
<li><p><a href="#repo"><b>Technical Tips</b></a>
<ul>
- <li><p><a href="#cvs">Basic CVS commands</a><p></li>
- <li><p><a href="#symlinks">Symbolic links</a><p></li>
- <li><p><a href="#refresh">Meta refresh (don't use)</a><p></li>
- <li><p><a href="#scripts">Server-side scripts</a><p></li>
- <li><p><a href="#sysadmins">System administrators</a><p></li>
- </ul><p></li>
+ <li><p><a href="#cvs">Basic CVS commands</a></p></li>
+ <li><p><a href="#symlinks">Symbolic links</a></p></li>
+ <li><p><a href="#refresh">Meta refresh (don't use)</a></p></li>
+ <li><p><a href="#scripts">Server-side scripts</a></p></li>
+ <li><p><a href="#sysadmins">System administrators</a></p></li>
+ </ul></p></li>
<li><p><a href="#UsefulResources"><b>Useful Resources</b></a>
<ul>
- <li><p><a href="#external-resources">External resources</a><p></li>
- <li><p><a href="#internal-resources">Internal resources</a><p></li>
- </ul><p></li>
+ <li><p><a href="#external-resources">External resources</a></p></li>
+ <li><p><a href="#internal-resources">Internal resources</a></p></li>
+ </ul></p></li>
</ul>
<hr class="no-display" />
</div>
@@ -148,39 +148,39 @@
<ul class="para">
<li><p>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.<p></li>
+prepare pages for the GNU web server.</p></li>
<li><p>The GNU website lists and links
<strong>only</strong> to free software. The software's source code and
executables have to be freely redistributable and modifiable to and by
all people and organizations. If in doubt, ask <a
-href="mailto:gnu@gnu.org";><gnu@gnu.org></a>.<p></li>
+href="mailto:gnu@gnu.org";><gnu@gnu.org></a>.</p></li>
<li><p>The GNU website gives priority to software covered by either
the <a href="/licenses/gpl-3.0.html">GNU General Public License</a> or the
-<a href="/licenses/lgpl-3.0.html">GNU Lesser General Public
License</a>.<p></li>
+<a href="/licenses/lgpl-3.0.html">GNU Lesser General Public
License</a>.</p></li>
<!-- What does this mean exactly? -->
<li><p>Before you take any graphics or text from another website,
please ask for permission to use it. It's polite to do so. It is also
-essential for us to avoid copyright infringement.<p></li>
+essential for us to avoid copyright infringement.</p></li>
<li><p>Before adding a link, check that it follows our <a
-href="#pollinking">linking criteria</a>.<p></li>
+href="#pollinking">linking criteria</a>.</p></li>
<li><p>Do not list an address of an individual, including the
maintainer of a GNU package, unless explicitly asked to have it
listed. Most GNU maintainers do not want a lot of extra mail and prefer
to get bug reports and other messages from the relevant <a
-href="/prep/mailinglists.html">mailing lists</a>.<p></li>
+href="/prep/mailinglists.html">mailing lists</a>.</p></li>
<li><p>Pages should not load CSS from servers other than those run
-by the FSF.<p></li>
+by the FSF.</p></li>
<li><p>Generally, the use of JavaScript is not allowed. Exceptions to
this need to be reviewed and approved by the
<a href="/people/webmeisters.html"> Chief GNUisance</a> on a
-case-by-case basis.<p></li>
+case-by-case basis.</p></li>
</ul>
@@ -189,21 +189,21 @@
<ul class="para">
<li><p>Every page should have a copyright notice listing the copyright
-holder(s) and copyright year(s).<p></li>
+holder(s) and copyright year(s).</p></li>
<li><p>Every page should have a notice giving everyone permission
to distribute it. If you cannot get such a permission from the author,
please discuss the issue with the webmasters before posting it. This
-applies to CSS as well as to HTML.<p></li>
+applies to CSS as well as to HTML.</p></li>
<li><p>Normally you shouldn't post a page that isn't copyright FSF unless
we have permission to modify the version we publish. If you cannot
get such a permission from the author, please discuss the issue with
-the FSF before posting it. This applies to CSS as well as to HTML.<p></li>
+the FSF before posting it. This applies to CSS as well as to HTML.</p></li>
<li><p>If ultimately we decide to post a new page we don't have permission to
modify, put the text “Posted in 20XX without FSF permission to
-modify” inside an HTML comment, just after the copyright notice.<p></li>
+modify” inside an HTML comment, just after the copyright notice.</p></li>
<li><p>All pages that explain how to do something, such as how to use
certain programs, are documentation. This includes all the pages in
@@ -213,10 +213,10 @@
a <a href="/licenses/license-recommendations.html">free
license</a>. If such a page doesn't have a free license, please report the
problem to <a
-href="mailto:webmasters@gnu.org";><webmasters@gnu.org></a>.<p></li>
+href="mailto:webmasters@gnu.org";><webmasters@gnu.org></a>.</p></li>
<li><p>For other pages, use the same license as some other page that serves
-a similar kind of purpose.<p></li>
+a similar kind of purpose.</p></li>
</ul>
@@ -226,13 +226,13 @@
<li><p>All public pages of the GNU website should be strictly compliant with
<a href="https://www.w3.org/TR/?status=rec";>W3C Recommendations (REC)</a>,
as opposed to Working Drafts (WD), Candidate Recommendations (CR),
-Proposed Recommendations (PR) or Retired Recommendations (RET).<p></li>
+Proposed Recommendations (PR) or Retired Recommendations (RET).</p></li>
-<li><p>HTML 5 and CSS3 are target for upgrade from older standards.<p></li>
+<li><p>HTML 5 and CSS3 are target for upgrade from older standards.</p></li>
<li><p>Regardless of the web standards used, all pages should meet the
<a href="https://www.w3.org/TR/2018/REC-WCAG21-20180605/";>Web Content
-Accessibility Guidelines (WCAG)</a>.<p></li>
+Accessibility Guidelines (WCAG)</a>.</p></li>
</ul>
@@ -246,13 +246,13 @@
<li><p>To make simultaneous edition of many files easier,
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.<p></li>
+explained next.</p></li>
<li><p>Each directory in the web server tree should have a
symbolic link named <code>index.html</code> to the top-level HTML file
for that directory. Use the <a
href="#symlinks"><code>.symlinks</code></a>
-file to handle this.<p></li>
+file to handle this.</p></li>
<li id="NamingTranslations">If you translate your web page (say,
<code><var>page</var>.html</code>) in different languages, please
@@ -265,7 +265,7 @@
rel="noopener">ISO 3166-1</a> (converted to 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>.<p></li>
+translation should be named <code>not-ipr.pt-br.html</code>.</p></li>
</ul>
@@ -279,20 +279,20 @@
<code><title></code> and <code><body></code>,
and always include the appropriate DTD or Schema reference in all markup
standards older than HTML 5.
-This appeases overly pedantic web browsers.<p></li>
+This appeases overly pedantic web browsers.</p></li>
<li><p>Do not add <code><!-- comments --></code> at the top of a
document. Old web browsers expect the doctype, XML declaration, or Schema to
be
at the top. Comments will confuse them, and often cause them to
incorrectly interpret your markup.<br />
If you <i>must</i> add a comment before <code><!DOCTYPE html></code>, then
-use <code><!--[if !IE]> comments <![endif]--></code>.<p></li>
+use <code><!--[if !IE]> comments <![endif]--></code>.</p></li>
<li><p>The <code><head></code> element should contain this line:
<p class="emph-box">
<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.<p></li>
+problems they find on a page.</p></li>
<li><p>The first header element, generally <code><h1></code> or
<code><h2></code>, should have
its text duplicated at the start of the <code><title></code> element.
@@ -303,13 +303,13 @@
users click on an item in these menus, they get a page with the expected
heading. Please properly use your headers in numerical order: 1, 2,
etc. These are not used for looks, but for the organization of the
-document.<p></li>
+document.</p></li>
<li><p>The <code><title></code> element should include the
phrases <i>“GNU Project”</i>
and <i>“Free Software Foundation”</i> so the pages can be better
indexed by external search engines. The default is to add this at the
-end: <code> - GNU Project - Free Software Foundation</code>.<p></li>
+end: <code> - GNU Project - Free Software Foundation</code>.</p></li>
</ul>
@@ -319,7 +319,7 @@
<li><p>All pages should have a footer. 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.<p></li>
+boilerplate</a>, referred below.</p></li>
<li><p>The footer should include the <a
href="#CopyrightGuidelines">copyright and license notices</a> for the
@@ -328,15 +328,15 @@
main text.<br />
The rules for listing copyright holders and years are detailed in
the <a href="/prep/maintain/html_node/Copyright-Notices.html">GNU
-Maintainers' guide</a>.<p></li>
+Maintainers' guide</a>.</p></li>
-<li><p>The Copyright Infringement Notification is a legal requirement.<p></li>
+<li><p>The Copyright Infringement Notification is a legal requirement.</p></li>
<li><p>In addition, the footer should have contact info for both the FSF (or
responsible party) and the address for bug reports (webmasters for
general pages, but project-specific addresses otherwise).
The reason to note this in the footer is so the user
-always finds this information at the same place on each page.<p></li>
+always finds this information at the same place on each page.</p></li>
</ul>
@@ -351,18 +351,18 @@
href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/
boilerplate.html?root=www&content-type=text%2Fplain">
original source</a> of the boilerplate instead, and follow the instructions
-in it.<p></li>
+in it.</p></li>
<!-- Impact on the transition toward HTML 5 and WCAG? -->
<li><p>The templated pages must follow the <a
href="https://www.w3.org/TR/xhtml1/";>XHTML-1.0 guidelines</a>.
Well-formedness is essential for translatable pages that need to be
-converted to POT files by the PO4A/Gettext tools.<p></li>
+converted to POT files by the PO4A/Gettext tools.</p></li>
<li><p>Our <abbr title="Server-Side Include">SSI</abbr>s declare UTF-8 as the
character encoding; using any other encoding is problematic.<br />See the
<a href="https://httpd.apache.org/docs/current/howto/ssi.html";>
-Introduction to Apache SSIs</a> to learn more on this topic.<p></li>
+Introduction to Apache SSIs</a> to learn more on this topic.</p></li>
</ul>
@@ -374,12 +374,12 @@
<ul class="para">
<li><p>On pages with dated entries (e.g., /philosophy/latest-articles.html),
the newer entries should be first; in other words, preserve reverse
-chronological order.<p></li>
+chronological order.</p></li>
<li><p>Offer a document in as many formats as the GNU Project has it.
For an example, see <a href="/licenses/fdl.html">The GNU Free
Documentation License</a>. This lets users get the document in the
-format most useful to them.<p></li>
+format most useful to them.</p></li>
</ul>
@@ -387,23 +387,23 @@
<ul class="para">
<li><p>English pages should follow the standard American spelling,
-hyphenation and punctuation conventions.<p></li>
+hyphenation and punctuation conventions.</p></li>
<li><p>Since these conventions are not always very specific, especially as
regards hyphenation and quotes, gnu.org adds its own rules for the sake of
consistency:
<ul>
<li><p>The term “nonfree” is preferred over
“non-free”;
- likewise, “noncommercial” over
“non-commercial.”<p></li>
+ likewise, “noncommercial” over
“non-commercial.”</p></li>
<li><p>In ordinary text, HTML entities
“<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.<p></li>
+ This doesn't apply to script-generated documents.</p></li>
<li><p>Where they exist, the double spaces after sentence breaks should be
- preserved. They enable Emacs sentence commands to do the right
thing.<p></li>
+ preserved. They enable Emacs sentence commands to do the right
thing.</p></li>
</ul>
-<p></li>
+</p></li>
</ul>
@@ -418,12 +418,12 @@
<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.<p></li>
+HTTPS.</p></li>
<li><p>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
-tolerated.<p></li>
+tolerated.</p></li>
<li><p>Don't use just a directory name in a URL; always include the
specific filename. For instance, use <code>/gnu/gnu.html</code>, not just
@@ -433,7 +433,7 @@
different URLs, the URLs that haven't been explicitly referenced will
not be highlighted as visited. So the user goes to pages he/she has
already seen, which is irritating. Also, this eases maintenance of the site
-as things get moved around.<p></li>
+as things get moved around.</p></li>
<li><p>When embedding static resources, such as videos that are not in
the <code>www</code> CVS repository along with the rest of the
@@ -444,7 +444,7 @@
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.<p></li>
+they can be used interchangeably.</p></li>
</ul>
@@ -452,7 +452,7 @@
<ul class="para">
<li><p>Be sure to omit the filename entirely when linking to an anchor in
-the same file, and double-check that the anchor actually works.<p></li>
+the same file, and double-check that the anchor actually works.</p></li>
<li><p>Consider others linking to your page when either removing an element
that carries an <code>id</code> attribute, or changing an <code>id</code>.
@@ -472,7 +472,7 @@
Please avoid moving the old <code>id</code> to a translatable string,
unless there is no other way to keep the markup valid. Translators will
-thank you!<p></li>
+thank you!</p></li>
</ul>
@@ -480,14 +480,14 @@
<ul class="para">
<li><p><em>Reminder:</em> before adding a link, check that it follows
our <a
-href="#pollinking">linking criteria</a>.<p></li>
+href="#pollinking">linking criteria</a>.</p></li>
<li><p>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).<p></li>
+a locked/green lock on most web browsers).</p></li>
<!--
<li><p>Protocol-relative URLs (e.g., <code>//www.example.org</code>) are not
-recommended when linking to external, third-party domains.<p></li>
+recommended when linking to external, third-party domains.</p></li>
-->
</ul>
@@ -500,7 +500,7 @@
standard email client) to clearly distinguish them from hypertext anchors.
See <a href="https://tools.ietf.org/html/rfc6068#section-6";>RFC 6068</a> for
advanced examples of how to use mailto URIs to specify a subject, the
-body, etc.<p></li>
+body, etc.</p></li>
<li><p>When citing people, place the <code>mailto:</code> anchor next to
their name, so that the email address is retained in printed copies of
@@ -516,7 +516,7 @@
<a href="https://www.stallman.org/";>Richard Stallman</a>
<a href="mailto:rms@gnu.org";><rms@gnu.org></a>
</p>
- <p></li>
+ </p></li>
<li><p>
<p>If the person doesn't own a website:</p>
<pre class="emph-box">
@@ -527,9 +527,9 @@
Richard Stallman
<a href="mailto:rms@gnu.org";><rms@gnu.org></a>
</p>
- <p></li>
+ </p></li>
</ul>
-<p></li>
+</p></li>
</ul>
@@ -538,21 +538,21 @@
<ul class="para">
<li><p>Never use <code><acronym></code>: HTML 5 obsoletes it
in
favor of <code><abbr></code>. The latter must be expanded in a
- <code>title</code> attribute.<p></li>
+ <code>title</code> attribute.</p></li>
<li><p>When an abbreviation may be unfamiliar to a reader, give its
expansion <i>only the first time</i> it is used in a document.<br />
Example: <code><abbr title="Expanded
Abbreviation">EA</abbr></code> or <code>EA
- (Expanded Abbreviation)</code>.<p></li>
+ (Expanded Abbreviation)</code>.</p></li>
<li><p>Make sure <code><abbr></code> is styled via CSS to meet the
accessibility guidelines. By default some browsers render it in an
- ugly way.<p></li>
+ ugly way.</p></li>
<li><p>For common-enough initialisms, such as GNU, FSF, BSD, RAM, HTML,
DVD, and so on, no markup is needed at all.
- Use your judgment.<p></li>
+ Use your judgment.</p></li>
</ul>
@@ -566,7 +566,7 @@
href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F49";>makes sense
when linearized</a>, and has <a
href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F91";>appropriately
-marked up headers</a>.<p></li>
+marked up headers</a>.</p></li>
<li><p>Some people like to organize links as a menu to
the left or right of the main text when using graphical browsers. That
@@ -579,7 +579,7 @@
visible on the first page when viewing it with a text browser. A
menu bar of one or two horizontal lines might accomplish your
purpose as well. Providing a “skip link” to the main text
-is another option (see the table of contents above for an example).<p></li>
+is another option (see the table of contents above for an example).</p></li>
</ul>
@@ -590,7 +590,7 @@
<ul class="para">
<li><p>Generic styling for desktops and smartphones is provided by <a
-href="/layout.css"><code>layout.css</code></a>; it covers most of our use
cases.<p></li>
+href="/layout.css"><code>layout.css</code></a>; it covers most of our use
cases.</p></li>
<li><p>Mobile devices with very limited resources use <a
href="/mini.css"><code>mini.css</code></a>.
@@ -599,23 +599,23 @@
and <a
href="https://yui.github.io/yui2/docs/yui_2.9.0_full/base/index.html";>base</a>
stylesheets, as these devices typically have minimal need for various
-fonts and no need for fancy layouts.<p></li>
+fonts and no need for fancy layouts.</p></li>
<li><p>Printers use <a href="/print.css"><code>print.css</code></a>. Note
that the header, navigation
-bars and footer (except copyright and license) are unprintable.<p></li>
+bars and footer (except copyright and license) are unprintable.</p></li>
<li><p>In addition to <code>layout.css</code>, some pages have specialized
stylesheets: <a
href="/graphics/graphics.css"><code>graphics.css</code></a> for the GNU
Art section, and <a
href="/side-menu.css"><code>side-menu.css</code></a> for the Malware and
-Education sections.<p></li>
+Education sections.</p></li>
<li><p>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
-style applies to a single element, it should normally be added as an
attribute.<p></li>
+style applies to a single element, it should normally be added as an
attribute.</p></li>
<li><p>If you specify any color attribute in the HTML, you should specify all
of
them that are allowed for that element. This is because some browsers
@@ -624,7 +624,7 @@
override the user's choices. In the worse case, the foreground and
background could end up the same. Please use a stylesheet for
this, and not HTML 3.2 (HTML 4 Transitional) deprecated
-markup.<p></li>
+markup.</p></li>
</ul>
@@ -634,25 +634,25 @@
<li><p>Historical pages (unmaintained translations for the most part) refer
to <a href="/gnu.css"><code>gnu.css</code></a>, which in turn loads
<code>mini.css</code>, as these pages are
-usually very basic, plain pages with little or no formatting.<p></li>
+usually very basic, plain pages with little or no formatting.</p></li>
<li><p>There are dedicated stylesheets for software manuals. The main ones
are:
<ul>
- <li><p><a href="/style.css"><code>style.css</code></a>;<p></li>
+ <li><p><a href="/style.css"><code>style.css</code></a>;</p></li>
<li><p><a href="/software/gnulib/manual.css"><code>gnulib.css</code></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>.<p></li>
+ regenerate Texinfo manuals</a>.</p></li>
</ul>
-<p></li>
+</p></li>
<li><p>Translators maintain stylesheets
(<code>/style.<var>lang</var>.css</code>)
that modify <code>layout.css</code> according to
their own needs. The RTL languages (Arabic, Persian, and Hebrew) use
<a href="/style.rtl.css"><code>style.rtl.css</code></a>. Please don't
forget to update <code>style.rtl.css</code> if you make LTR-specific
-changes to <code>layout.css</code>.<p></li>
+changes to <code>layout.css</code>.</p></li>
</ul>
@@ -676,12 +676,12 @@
<ul class="para">
<li><p>The webpages which are meaningful without media files (videos, graphics,
photos, animations, etc.) may be tested on modern, stable text-only browsers
-and should be accessible by text-only users.<p></li>
+and should be accessible by text-only users.</p></li>
<li><p>The subset of text-only browsers for compatibility testing is composed
by
stable and modern text mode browsers such as Lynx, Elinks and w3m, executed
on the latest stable xterm, with <i>at least</i> support for 24-bit color,
-italic/bold fonts and UTF-8 enabled.<p></li>
+italic/bold fonts and UTF-8 enabled.</p></li>
<li><p>The CSS media queries can be used to detect graphical web browsers and
their
capabilities, but may be ignored (always return <var>true</var>) on text-only
@@ -732,7 +732,7 @@
</code></pre>
<p>Always double-check the result on different web browsers.</p>
-<p></li>
+</p></li>
</ul>
<p>To maximize compatibility, assume the terminal buffer has 80 to 132 columns
@@ -758,14 +758,14 @@
extensions; a local transparent HTTP/S proxy can serve the same purpose; the
GNU/Linux kernel <abbr title="Traffic Control">TC</abbr> implements
<abbr title="Hierarchical Token Bucket">HTB</abbr>, which can be used to create
-advanced testing environments with throttled network interfaces.<p></li>
+advanced testing environments with throttled network interfaces.</p></li>
<li><p>We do not use background images on our pages, as they make text
significantly harder to read.<br />
If you are forced to add a background, ensure there is <a
href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F83";>sufficient
contrast</a> with text, graphs, … and remember that CSS gradients may
-not be rendered by accessibility tools.<p></li>
+not be rendered by accessibility tools.</p></li>
<li><p>In the past, GIFs have had patent problems. However, now that
the IBM and Unisys patents (and other patents worldwide that are
@@ -780,7 +780,7 @@
Other formats are also allowed, though JPEG is the one most widely
recognized by web browsers (avoid JPEG 2000, and be careful with PNG
alpha channels; the former is not widely supported, and the latter are
-not fully supported by some older browsers).<p></li>
+not fully supported by some older browsers).</p></li>
</ul>
@@ -790,7 +790,7 @@
<li><p>All images that are not purely decorative should provide <a
href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F83";>sufficient
contrast</a> between informative parts (text, graphs, etc.) and
-background.<p></li>
+background.</p></li>
<li><p><p>Always have a textual alternative for in-line images, to ensure
indexability by search engines and accessibility. For instance:</p>
@@ -827,7 +827,7 @@
their way to the translatable strings that are extracted by the
PO4A/Gettext tools.</p>
<div style="clear: both"></div>
-<p></li>
+</p></li>
<li id="image-size">Check that the image doesn't look too big or too small
when displayed at its original size, using the browser's default font
@@ -835,7 +835,7 @@
size with the width and height attributes.<br />
Specifying both width and height will reserve the space required for the
image during the page loading phase. Loading will thus be faster and
-smoother, especially on low-end machines with poor connectivity.<p></li>
+smoother, especially on low-end machines with poor connectivity.</p></li>
<li><p>Also adjust image width or height in a style attribute, using scalable
units such as <code>em</code> or <code>%</code>; for instance:
@@ -862,12 +862,12 @@
<code>height</code> will reserve the space required for the image during
the page loading phase, preventing incremental <a
href="https://developers.google.com/speed/docs/insights/browser-reflow";>
-layout reflows</a>.</p><p></li>
+layout reflows</a>.</p></p></li>
<li><p>Link all images that are displayed throughout the website to the
relevant page, usually in <code>/graphics/</code>.
This will allow users to quickly go to pages related to the pictures they
-are interested in. See the next section for an example.<p></li>
+are interested in. See the next section for an example.</p></li>
</ul>
@@ -903,7 +903,7 @@
</p>
</pre>
<div style="clear: both"></div>
-<p></li>
+</p></li>
<li><p><p>If the image you are adding is 12em wide or more, and the page is
templated, you may find it convenient to use one of the responsive
@@ -933,10 +933,10 @@
inherit <code>max-width</code> on all web browsers (i.e., always test for
compatibility when you need to put a table beside a picture).</p>
<div style="clear: both"></div>
-<p></li>
+</p></li>
<li><p><a href="/graphics/graphics.css"><code>graphics.css</code></a> has
-some other layouts.<p></li>
+some other layouts.</p></li>
</ul>
@@ -1108,14 +1108,14 @@
<h4 id="cvs">Basic CVS commands</h4>
<ul class="para">
-<li><p>For the offline reference manual, execute <kbd>info cvs</kbd>.<p></li>
+<li><p>For the offline reference manual, execute <kbd>info cvs</kbd>.</p></li>
<li><p>
Before the initial checkout, set the environment variable
<kbd>CVS_RSH=ssh</kbd>.<br />Alternatively, 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> to use an external ssh program.<p></li>
+<code>:extssh:</code></a> to use an external ssh program.</p></li>
<li><p>
<p>If you have write access to the main repository of www.gnu.org, check
@@ -1127,7 +1127,7 @@
<p>You will get a working directory, <code>www</code>, with the same
structure as our main website.</p>
-<p></li>
+</p></li>
<li><p>
<p>If you don't have write access to the main repository, you can still
@@ -1136,7 +1136,7 @@
<pre class="emph-box">
<kbd>cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/web/www co www</kbd>
</pre>
-<p></li>
+</p></li>
<li><p>
<p>Check out the <strong>web</strong> repository of the
<var>fooproject</var>:</p>
@@ -1156,7 +1156,7 @@
href="/server/standards/README.webmastering.html#gnupackages">Web pages for
official GNU software</a> before committing anything to the web repository
of a software project.</em></p>
-<p></li>
+</p></li>
<li><p>
<p>Add a file or directory:</p>
@@ -1164,7 +1164,7 @@
<pre class="emph-box">
<kbd>cvs add <var>foo</var></kbd>
</pre>
-<p></li>
+</p></li>
<li><p>
<p>Update before you edit a file:</p>
@@ -1172,7 +1172,7 @@
<pre class="emph-box">
<kbd>cvs update -P <var>foo</var></kbd>
</pre>
-<p></li>
+</p></li>
<li><p>
<p>Check the changes you are going to commit:</p>
@@ -1180,7 +1180,7 @@
<pre class="emph-box">
<kbd>cvs diff -U2 <var>foo</var></kbd>
</pre>
-<p></li>
+</p></li>
<li><p>
<p>Perform the commit (no need for <kbd>cvs add</kbd> if the file is
@@ -1204,7 +1204,7 @@
<p>The changes (except to <a href="#symlinks">.symlinks files</a>) should
be visible on www.gnu.org within minutes.</p>
-<p></li>
+</p></li>
</ul>
<p>For further details on CVS, such as reverting to a previous version, or
@@ -1236,10 +1236,10 @@
as described below:</p>
<ul>
-<li><p>Lines starting with a sharp sign (“#”) are ignored.<p></li>
+<li><p>Lines starting with a sharp sign (“#”) are ignored.</p></li>
<li><p>Lines that do not contain two strings separated by white space are
silently
-ignored.<p></li>
+ignored.</p></li>
</ul>
<p>Here is an example of <code>.symlinks</code>, which redirects a file to
@@ -1307,12 +1307,12 @@
Please don't use this method for new redirections, as some browsers (e.g.,
Firefox) prevent the redirection from happening without user input. This
is a security feature, but many people find it annoying, and it can
-disorient some impaired users.<p></li>
+disorient some impaired users.</p></li>
<li><p>Automatic refresh should be avoided too, because of its <a
href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F41";>accessibility
issues</a>. If updating is necessary, provide a
-<a href=""><button style="cursor:pointer">Reload page</button></a>
button.<p></li>
+<a href=""><button style="cursor:pointer">Reload page</button></a>
button.</p></li>
</ul>
<h4 id="scripts">Server-side scripts</h4>
@@ -1344,13 +1344,13 @@
href="https://www.w3.org/TR/2018/SPSD-xhtml1-20180327/";>XHTML 1.0</a>,
<a href="https://www.w3.org/TR/html52/";>HTML 5.2</a>, and
<a href="https://www.w3.org/TR/2018/REC-WCAG21-20180605/";>WCAG 2.1</a>
- recommendations.<p></li>
+ recommendations.</p></li>
<li><p>The <abbr title="Mozilla Developer Network">MDN</abbr>
<a href="https://developer.mozilla.org/en-US/docs/Learn";>Learning Area</a>
provides reliable specifications, guides and tutorials for beginners. It
cannot replace the aforementioned official W3C specifications but it often
- provides useful clarifications.<p></li>
+ provides useful clarifications.</p></li>
<li><p>The <a
href="https://www.anybrowser.org/campaign/"; rel="noopener"
@@ -1365,7 +1365,7 @@
provide <em>informal tips</em> to ensure that a website is able to convey
information to the largest audience possible. If a page does not obtain a
satisfying positioning on public search engines then dedicated
- <abbr title="Search Engine Optimization">SEO</abbr> becomes
necessary.<p></li>
+ <abbr title="Search Engine Optimization">SEO</abbr> becomes
necessary.</p></li>
</ul>
<h4 id="internal-resources">Internal resources</h4>
@@ -1373,40 +1373,40 @@
<p>This section contains references managed by us.</p>
<ul>
- <li><p><a href="#content">The GNU Website Guidelines</a> (this
page);<p></li>
+ <li><p><a href="#content">The GNU Website Guidelines</a> (this
page);</p></li>
<li><p>Guidelines for
<a href="/server/standards/README.editors.html">Web Page Creation</a> at
- www.gnu.org;<p></li>
+ www.gnu.org;</p></li>
<li><p><a href="/software/texinfo/manual/texinfo/html_node/Tips.html">
Appendix B Tips and Hints</a>, and other style tips in the <a
- href="/software/texinfo/manual/texinfo/">Texinfo Manual</a>;<p></li>
+ href="/software/texinfo/manual/texinfo/">Texinfo Manual</a>;</p></li>
<li><p><a href="/accessibility/accessibility.html">GNU Accessibility
- Statement</a>;<p></li>
+ Statement</a>;</p></li>
<li><p><a href="/server/standards/README.webmastering.html">GNU
- Webmastering Guidelines</a>;<p></li>
+ Webmastering Guidelines</a>;</p></li>
<li><p>Guide to
<a href="/server/standards/README.translations.html">translating</a> GNU
- web pages into other languages;<p></li>
+ web pages into other languages;</p></li>
<li><p><a
href="/software/trans-coord/manual/gnun/html_node/Webmaster-Tips.html">
- Tips for webmasters</a> to make translators' job easier;<p></li>
+ Tips for webmasters</a> to make translators' job easier;</p></li>
<li><p><a href="//savannah.gnu.org/maintenance/FrontPage/">Documentation
for
- Savannah</a>, the SourceForge clone dedicated to the GNU Project;<p></li>
+ Savannah</a>, the SourceForge clone dedicated to the GNU Project;</p></li>
<li><p><a href="/prep/gnumaint/README">
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 <code>www</code>);<p></li>
+ the <code>/*/allgnupkgs.html</code> files in <code>www</code>);</p></li>
<li><p><a href="/server/tasks.html">How to help</a> with our
- <a href="/server/server.html">web server</a>.<p></li>
+ <a href="/server/server.html">web server</a>.</p></li>
</ul>
</div><!-- for id="content", starts in the include above -->
@@ -1467,7 +1467,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2021/04/26 14:22:15 $
+$Date: 2021/04/26 14:31:05 $
<!-- timestamp end --></p>
</div>
</div><!-- for class="inner", starts in the banner include -->
- www/server/standards gnu-website-guidelines.html, Lorenzo L. Ancora, 2021/04/10
- www/server/standards gnu-website-guidelines.html, Lorenzo L. Ancora, 2021/04/10
- www/server/standards gnu-website-guidelines.html, Therese Godefroy, 2021/04/11
- www/server/standards gnu-website-guidelines.html, Ineiev, 2021/04/12
- www/server/standards gnu-website-guidelines.html, Therese Godefroy, 2021/04/14
- www/server/standards gnu-website-guidelines.html, Therese Godefroy, 2021/04/14
- www/server/standards gnu-website-guidelines.html, Therese Godefroy, 2021/04/14
- www/server/standards gnu-website-guidelines.html, Lorenzo L. Ancora, 2021/04/26
- www/server/standards gnu-website-guidelines.html,
Lorenzo L. Ancora <=
- www/server/standards gnu-website-guidelines.html, Therese Godefroy, 2021/04/26
- www/server/standards gnu-website-guidelines.html, Ineiev, 2021/04/27
- www/server/standards gnu-website-guidelines.html, Jason Self, 2021/04/29