<!--#include virtual="/server/html5-header.html" -->
<!-- Parent-Version: 1.96 -->
<title>Guidelines for Writing Web Pages for www.gnu.org
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/server/standards/po/README.editors.translist" -->
<!--#include virtual="/server/banner.html" -->
<div class="reduced-width">
<h2>Guidelines for Writing Web Pages for www.gnu.org</h2>
<div class="thin"></div>

<p>This is a general guide for everyone who wishes to write a web page for 
<code>www.gnu.org</code>. There are several other important guides,
most notably the <a
href="/server/standards/gnu-website-guidelines.html">GNU Website
Guidelines</a>. A <a
href="/server/standards/gnu-website-guidelines.html#UsefulResources">
list of other useful resources</a> is also available.</p>

<p>
<strong>No pages on the GNU Project web server should ever make any
references to nonfree software or documentation.</strong>
This is VERY important.
</p>

<p>
A good start when writing a web page is to <a
href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/
boilerplate.html?root=www&content-type=text%2Fplain">
href="/server/standards/boilerplate-source.txt">
use the boilerplate</a>, and follow 
the instructions in it. Please delete the unneeded comments as you go.
It makes the HTML source file easier for future maintainers to work with.
</p>

<p>
The web page(s) of your program should provide the basic information
that users are looking for:
</p>
<ul>
	<li>a description on what the program does,</li>
	<li>where to download the program in question,</li>
	<li>where to report bugs,</li>
	<li>FAQs and documentation if they are available, and</li>
	<li>installation instructions.</li>
</ul>

<p>
The description should be long enough for people to grasp the whole
program, but not so long that they get bored reading it. If a package
consists of several smaller programs, it is best to write a general
description of what types of programs are included in the package, and
then write a shorter description for each program.
</p>

<p>
The GNU Project would like to host the web pages of all GNU programs. So,
if the main pages of your program are currently on some other server,
please consider moving them to <a href="https://savannah.gnu.org/">
our hosting facility (Savannah)</a>.
</p>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.  Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        <web-translators@gnu.org></a>.</p>

        <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 contributing translations
of this article.</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright (C) 1999, 2011, 2012, 2014, 2018, 2021 2021, 2022, 2025 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2025/05/06 09:32:20 $
<!-- timestamp end --></p>
</div>
</div>
</body>
</html>