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

[Therese Godefroy]

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 21/02/07 16:18:48

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

Log message:
        Update the description of stylesheets.

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

Patches:
Index: gnu-website-guidelines.html
===================================================================
RCS file: /webcvs/www/www/server/staging/standards/gnu-website-guidelines.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnu-website-guidelines.html 7 Feb 2021 18:38:17 -0000       1.2
+++ gnu-website-guidelines.html 7 Feb 2021 21:18:47 -0000       1.3
@@ -112,7 +112,7 @@
 
 <ul>
 <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&amp;content-type=text%2Fplain">
+href="https://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
@@ -386,7 +386,7 @@
 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="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain">
+href="https://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>
 
@@ -404,22 +404,26 @@
 <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&nbsp;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>
+<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>
 
 <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, 
as these
-devices typically have minimal need for various fonts and no need for
-fancy layouts.</li>
+This stylesheet is just the YUI (version&nbsp;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>If some special styling is needed for a specific page, it should be added
 to the page itself in a &lt;style&gt; element, between the SSI directives
 that include <code>header.html</code> and <code>banner.html</code>. If the
@@ -437,9 +441,9 @@
 <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="//web.archive.org/web/20190917161357/http://yuilibrary.com/yui/docs/cssgrids/";>
+href="https://web.archive.org/web/20190917161357/http://yuilibrary.com/yui/docs/cssgrids/";>
 YUI version&nbsp;3</a>, and <a
-href="//purecss.io/grids/">Pure Grids</a>. The components provided by
+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>
 
@@ -452,7 +456,16 @@
 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;</li>
+  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.<var>lang</var>.css</code>) 
that
 modify layout.css according to their own needs.  The RTL languages (Arabic,
@@ -977,7 +990,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="//savannah.gnu.org/maintenance/FrontPage/">Documentation for
+    <li><a 
href="https://savannah.gnu.org/maintenance/FrontPage/";>Documentation for
     Savannah</a>, the SourceForge clone dedicated to the GNU Project;</li>
 
     <li><a href="/prep/gnumaint/README">
@@ -1050,7 +1063,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/02/07 18:38:17 $
+$Date: 2021/02/07 21:18:47 $
 <!-- timestamp end --></p>
 </div>
 </div><!-- for class="inner", starts in the banner include -->