Annotation of htdocs/developers/htdocs.xml, revision 1.8

1.1       jschauma    1: <?xml version="1.0"?>
                      2: <!DOCTYPE webpage
                      3:   PUBLIC "-//Norman Walsh//DTD Website V2.2//EN"
                      4:     "http://docbook.sourceforge.net/release/website/2.2/website.dtd" [
                      5: 
                      6: <!ENTITY % man-refs.ent SYSTEM "../share/xml/man-refs.ent"> %man-refs.ent;
                      7: 
                      8: ]>
                      9: 
                     10: <webpage id="htdocs">
                     11: <config param="desc" value="Editing htdocs"/>
1.8     ! jschauma   12: <config param="cvstag" value="$NetBSD: htdocs.xml,v 1.7 2004/11/27 21:47:51 jschauma Exp $"/>
        !            13: <config param="rcsdate" value="$Date: 2004/11/27 21:47:51 $"/>
1.1       jschauma   14: <head>
                     15: <title>Editing htdocs</title>
                     16: </head>
                     17: 
                     18: <sect1 id="editing-htdocs">
                     19: 
                     20: <itemizedlist>
                     21:        <listitem>
                     22:                <ulink url="#general">General notes on htdocs</ulink>
                     23:                <itemizedlist>
                     24:                        <listitem><ulink url="#who-can-edit">Who can edit htdocs</ulink></listitem>
                     25:                        <listitem><ulink url="#what-is-required">What is required to edit htdocs</ulink></listitem>
                     26:                        <listitem><ulink url="#validate-html">Validate your HTML</ulink></listitem>
                     27:                        <listitem><ulink url="#netbsd-org">NetBSD.org naming scheme</ulink></listitem>
                     28:                        <listitem><ulink url="#dotlist-files">What are .list files?</ulink></listitem>
                     29:                        <listitem><ulink url="#convert-to-xml">Converting to XML</ulink></listitem>
                     30:                        <listitem><ulink url="#dotxml-files">Processing .xml (docbook-website) files</ulink></listitem>
                     31:                        <listitem><ulink url="#moving-files">Renaming or moving files</ulink></listitem>
                     32:                        <listitem><ulink url="#flaglinks">What is the reasoning behind the flag links with empty.gif?</ulink></listitem>
                     33:                        <listitem><ulink url="#webserver">How do the pages get to the web server, and when?</ulink></listitem>
                     34:                </itemizedlist>
                     35:        </listitem>
                     36:        <listitem>
                     37:                <ulink url="#specific">Adding to specific areas</ulink>
                     38:                <itemizedlist>
                     39:                        <listitem><ulink url="#adding-news-items">Adding News Items</ulink></listitem>
                     40:                        <listitem><ulink url="#adding-events">Adding Events</ulink></listitem>
                     41:                        <listitem><ulink url="#adding-mailinglists">Adding to/editing the MailingLists page</ulink></listitem>
                     42:                        <listitem><ulink url="#consultants">Consultants for hire</ulink></listitem>
                     43:                </itemizedlist>
                     44:        </listitem>
                     45:        <listitem>
                     46:                Related Documentation:
                     47:                <itemizedlist>
                     48:                        <listitem><ulink url="announce.html">News story guidelines</ulink></listitem>
                     49:                        <listitem><ulink url="translate.html">Translating htdocs</ulink></listitem>
                     50:                </itemizedlist>
                     51:        </listitem>
                     52: </itemizedlist>
                     53: 
                     54: <html:hr/>
                     55: 
                     56: <sect2 id="general">
                     57: <title>General notes on htdocs</title>
                     58: 
                     59: <sect3 id="who-can-edit">
                     60: <title>Who can edit htdocs</title>
                     61: <para>
                     62:     Anyone with write access to the NetBSD CVS tree can checkout
                     63:     htdocs and make changes, and in fact is encouraged to do so.
                     64:     In particular as developers add features and drivers they should
                     65:     update the appropriate hardware or port homepage. Use your
                     66:     NetBSD.org login against cvs.NetBSD.org and checkout 'htdocs'.
                     67: </para>
                     68: <para>
                     69:     Users without CVS commit access are encouraged to check out htdocs
                     70:     via anoncvs, and mail patches to www@NetBSD.org, see 
                     71:     <ulink url="#dotlist-files">below</ulink>.
                     72: </para>
                     73: </sect3>
                     74: 
                     75: <sect3 id="what-is-required">
                     76: <title>What is required to edit htdocs</title>
                     77: <para>
                     78:     <itemizedlist>
                     79:     <listitem>Read <ulink url="cvs-repos/cvs_intro.html">the CVS introduction</ulink>.</listitem>
                     80:     <listitem>Install <pkg>meta-pkgs/netbsd-www,</pkg> which provides the tools
                     81:        required to build the web site.</listitem>
                     82:     <listitem>Set your CVSROOT as indicated and run
                     83:        <para><programlisting>cvs checkout htdocs</programlisting></para></listitem>
                     84:     <listitem>Edit your preferred file, type <code><emphasis role="bold">make</emphasis></code> to rebuild
                     85:        the output files (if necessary).</listitem>
                     86:     <listitem>Check the results using <code><emphasis role="bold">cvs diff</emphasis></code>, and <code><emphasis role="bold">cvs
                     87:        commit</emphasis></code> if everything is good.</listitem>
                     88:     </itemizedlist>
                     89: </para>
                     90: </sect3>
                     91: 
                     92: <sect3 id="validate-html">
                     93: <title>Validate your HTML</title>
                     94: <para>
                     95:     After making any changes you should run your html through an HTML
                     96:     verifier such as <pkg>www/weblint,</pkg> or better still <ulink
                     97:     url="http://validator.w3.org/">http://validator.w3.org/</ulink>.
                     98:     The URL for a link to an index.html file should not include the
                     99:     trailing index.html.
                    100:     If you use weblint you may want to add the following to your
                    101:     <code>~/.weblintrc</code>.
                    102: </para>
                    103: <para>
                    104:     <programlisting>extension Netscape</programlisting>
                    105: </para>
                    106: </sect3>
                    107: 
1.3       symka     108: <sect3 id="NetBSD-org">
1.1       jschauma  109: <title>NetBSD.org naming scheme</title>
                    110: <para>
                    111:     Make sure you use NetBSD.org and not any other scheme (&#78;etbsd.org,
                    112:     &#110;etbsd.org, ...) in links, mailto's or other pointers. 
                    113: </para>
                    114: </sect3>
                    115: 
                    116: <sect3 id="dotlist-files">
                    117: <title>What are .list files?</title>
                    118: <para>
                    119:     <emphasis role="bold">The <code>.list</code> files are
                    120:     obsolete!</emphasis><html:br/>
                    121:     Please see <ulink url="#dotxml-files">this section</ulink> for details.
                    122:     The paragraphs below still apply to the currently existing <code>.list</code>
                    123:     files.
                    124: </para>
                    125: <para>
                    126:     A <code>.list</code> file contains standard HTML with additional special
                    127:     tags to simplify formatting. It used to be processed by <code><ulink
                    128:     url="../list2html.pl">list2html.pl</ulink></code> into the desired .html
1.2       jschauma  129:     file.  Since the <code>.list</code> files are now obsolete, they should not be
1.1       jschauma  130:     edited anymore.  If they need to be changed, they should be <ulink
                    131:     url="#convert-to-xml">converted to XML</ulink>.
                    132: </para>
                    133: <para>
                    134:     There should be a Makefile in each directory which handles processing
                    135:     the .list files into .html, and will recurse into any subdirs
                    136:     containing Makefiles.
                    137: </para>
                    138: <para>
                    139:     Continuation lines are understood (useful for the special tags).
                    140: </para>
                    141: <para>
                    142:     If you do not have CVS access and wish to submit changes, you
                    143:     can check out htdocs via anonymous CVS (see the <ulink
                    144:     url="cvs-repos/cvs_intro.html">NetBSD CVS HOWTO</ulink>). The best
                    145:     approach is usually to:
                    146:     <orderedlist>
                    147:        <listitem>Checkout the <emphasis>htdocs</emphasis> module
                    148:            <para><programlisting>cvs checkout htdocs</programlisting></para></listitem>
                    149:        <listitem>Edit the desired file. Most FAQ-style documents are
                    150:            generated from <code>.list</code> files, so it is best to check
                    151:            before editing.</listitem>
                    152:        <listitem>Run 'make' if you have edited .list or similar files.</listitem>
                    153:        <listitem><ulink url="#validate-html">Validate</ulink> the HTML. (Repeat
                    154:            these three steps as necessary).</listitem>
                    155:        <listitem>Submit a diff to &lt;<ulink url="mailto:www@NetBSD.org">www@NetBSD.org</ulink>&gt;
                    156:            using <emphasis role="bold">cvs diff</emphasis>, eg.
                    157:             <para><programlisting>cvs diff -u <emphasis>htdocs/path/to/file.list</emphasis></programlisting></para>
                    158:         </listitem>
                    159:     </orderedlist>
                    160: </para>
                    161: <para>
                    162:     You should run <emphasis role="bold">make</emphasis> before committing. You will need
                    163:     <pkg>lang/perl5</pkg> installed.
                    164: </para>
                    165: </sect3>
                    166: 
                    167: <sect3 id="convert-to-xml">
                    168: <title>Converting to XML</title>
                    169: <para>
                    170:     In order to facilitate global changes, we are currently converting the
                    171:     NetBSD website to XML (docbook-website).  As of 2004-11-15, any non-XML
                    172:     file that needs to be edited shall be converted to XML at the same time.
                    173:     You may find the script <code>htutils/scripts/list2xml</code> helpful to
                    174:     initiate the conversion of the old <code>.list</code> as well as plain
1.5       jschauma  175:     <code>.html</code> files.  Please note, however, that this script only
                    176:     does a few simple replacements of tags, and you will need to do a lot by
                    177:     hand after running it.  In particular, you need to make sure that all
                    178:     tags are closed in the proper order.
                    179: </para>
                    180: <para>
                    181:     When creating or converting <code>.xml</code> files, please make sure to
                    182:     add a <quote>id</quote> attribute to each <code>&lt;sect[1-4]&gt;</code>
1.8     ! jschauma  183:     as well as each <code>&lt;table&gt; tag:  this will prevent
        !           184:     <command>xsltproc</command> to generate an ID
1.5       jschauma  185:     itself, which would require an update of the resulting <code>.html</code>
                    186:     file after each regeneration.
                    187: </para>
                    188: <para>
                    189:     If you are unsure how to convert a given HTML tag to the XML equivalent,
                    190:     you may find some useful examples installed as part of the
                    191:     <pkg>textproc/docbook-website</pkg> on your system.  And of course you can
                    192:     feel free to ask on the www@ list for help.
1.1       jschauma  193: </para>
                    194: <para>
1.7       jschauma  195:     If you want an autogenerated TOC, you will need to set the depth of the
                    196:     TOC you would like by specifing <code>TOC_LEVEL=3</code> (for example)
                    197:     in the Makefile.  If you wish to exclude sections from the TOC, you can
                    198:     give them a <code>role=<quote><emphasis>NotInToc</emphasis></quote></code>
                    199:     attribute:
                    200:     <programlisting>&lt;sect2 id="not-in-toc" role="NotInToc"&gt;</programlisting>
                    201: </para>
                    202: <para>
1.1       jschauma  203:     After converting a file to XML, remember to add it to the
1.5       jschauma  204:     <code>htdocs/layout.xml</code> file and regenerate the website.  See
                    205:     <ulink url="#dotxml-files">below</ulink> for details.
1.1       jschauma  206: </para>
                    207: </sect3>
                    208: 
                    209: <sect3 id="dotxml-files">
                    210: <title>Processing .xml (docbook-website) files</title>
                    211: <para>
                    212:     In order to build .html files from .xml files, you will need at
                    213:     least <pkg>textproc/libxslt</pkg> and <pkg>textproc/docbook-website</pkg>
                    214:     installed. These are installed as part of <pkg>meta-pkgs/netbsd-www</pkg>
                    215: </para>
                    216: <para>
                    217:     To regenerate, cd to htdocs/ and run
                    218:       <para><programlisting>make ./autolayout.xml</programlisting></para>
                    219:     Then run <code><emphasis role="bold">make</emphasis></code> in the target directory.
                    220: </para>
                    221: </sect3>
                    222: 
                    223: <sect3 id="moving-files">
                    224: <title>Renaming or moving files</title>
                    225: <para>
                    226: In order to move or rename files within htdocs, the following procedure is
                    227: recommended:
                    228: 
                    229: <itemizedlist>
                    230:  <listitem>copy the file from the original location to new location</listitem>
                    231:  <listitem>modify html of the original file:
                    232:    <itemizedlist>
                    233:      <listitem>include a
                    234:          <code>&lt;META HTTP-EQUIV=Refresh CONTENT="5; URL=new-location"&gt;</code>
                    235:          tag in the header</listitem>
                    236:      <listitem>remove all content except the header and the footer</listitem>
                    237:      <listitem>add a sentence saying that the page moved and hyperlink it to the new
                    238:          location</listitem>
                    239:    </itemizedlist></listitem>
                    240:   <listitem>cvs add the new file</listitem>
                    241:   <listitem>cvs commit the new file and the changes of the old file at the same
                    242:       time, so we have some cvs reference of when and why things moved</listitem>
                    243: </itemizedlist>
                    244: </para>
                    245: </sect3>
                    246: 
                    247: <sect3 id="flaglinks">
                    248: <title>What is the reasoning behind the flag links with empty.gif?</title>
                    249: <para>
                    250:     Each NetBSD 'flag' links at the base of each page has:
                    251:     <itemizedlist>
                    252:     <listitem>href containing netbsd-banner with no alt tag</listitem>
                    253:     <listitem>href containing empty gif with "NetBSD" alt tag and the
                    254:         words "Home Page"</listitem>
                    255:     </itemizedlist>
                    256:     This has the effect of:
                    257:     <itemizedlist>
                    258:     <listitem>Making the "NetBSD Home Page" link a single link in lynx,
                    259:        i.e. not a NetBSD link and a Home Page link.</listitem>
                    260:     <listitem>In netscape, causing the additional text to be centered and
                    261:         aligned "better" w.r.t the graphic.  Without it, at least
                    262:         in netscape, they show up at the bottom not centered
                    263:         vertically, and abut the graphic (or, if you include spaces,
                    264:         include nasty underlined blanks which looks broken).</listitem>
                    265:     </itemizedlist>
                    266:     It's a grotty hack, but it makes things look right.
                    267: </para>
                    268: </sect3>
                    269: 
                    270: <sect3 id="webserver">
                    271: <title>How do the pages get to the web server, and when?</title>
                    272: <para>
                    273:     The NetBSD webpages are stored in CVS in the "htdocs" repository.
                    274:     For security reasons, the htdocs repository is copied (via rsync)
                    275:     to www.NetBSD.org each hour, and the a local checkout is done from
                    276:     that copy of the repository. The checked out tree can be found in
                    277:     "<code>/NetBSD-www</code>". The repository is updated and checked out
                    278:     every hour, about 40 minutes after the full hour (*:40). If you
                    279:     make a commit to htdocs, it will take up to an hour before the
                    280:     changes show up.
                    281: </para>
                    282: <para>
                    283:     Note that there are several files like the Gnats database
                    284:     (<ulink url="http://www.NetBSD.org/Gnats/"/>), the pkgsrc and source changes
                    285:     in Changes/changes*.html and Changes/pkg-changes*.html, the RSS
                    286:     files in Changes/rss-*.xml etc. that are not part of htdocs but
                    287:     that get generated by various scripts out of cron jobs directly on
                    288:     the web server. Check out "htutils/changes/*" to get access to the
                    289:     scripts.
                    290: </para>
                    291: </sect3>
                    292: 
                    293: </sect2>
                    294: 
                    295: <sect2 id="specific">
                    296: <title>Adding to specific areas</title>
                    297: 
                    298: <sect3 id="adding-gallery-entries">
                    299: <title>Adding to the 'Sites running NetBSD' gallery</title>
                    300: <para>
                    301: If you have a <code>NETBSD GALLERY ADDITION</code> email from the <ulink
                    302: url="../gallery/addsite.html">htdocs/gallery/addsite.html</ulink> page:
                    303: <orderedlist>
                    304: <listitem>Ensure you have perl installed</listitem>
                    305: <listitem>Save the message in your copy/paste buffer </listitem>
                    306: <listitem><code>cd htdocs/gallery</code></listitem>
                    307: <listitem><code>./addsite.pl</code>, paste the buffer, add a ^D, and answer '<code>y</code>' if it parsed OK.</listitem>
                    308: <listitem><code>cvs commit</code></listitem>
                    309: </orderedlist>
                    310: Alternatively you can manually edit <code>htdocs/gallery/sites.data</code>, and
                    311: run <code>make</code>.
                    312: </para>
                    313: </sect3>
                    314: 
                    315: <sect3 id="adding-news-items">
                    316: <title>Adding News Items</title>
                    317: <para>
                    318: Most news items go into <ulink
1.4       jschauma  319: url="../Changes/">htdocs/Changes/index.xml</ulink> (see note on
                    320: <ulink url="#dotxml-files">.xml files</ulink>).  Changes affecting a
1.1       jschauma  321: specific port should also be linked to from their htdocs/Port/*/ news section.
                    322: </para>
                    323: <para>
                    324: Important code news items should also be noted in the text
1.6       jschauma  325: <currentsrc>src/doc/CHANGES</currentsrc>
1.1       jschauma  326: file.
                    327: </para>
                    328: <para>Quick ``howto'' for the impatient (but please do read on for details):
                    329: <itemizedlist>
                    330: <listitem>cd htdocs/Changes</listitem>
                    331: <listitem>make update</listitem>
1.4       jschauma  332: <listitem>${EDITOR} index.xml</listitem>
1.1       jschauma  333: <listitem>make</listitem>
                    334: <listitem>make MSG="I added important NEWS!" commit</listitem>
                    335: </itemizedlist>
                    336: </para>
                    337: 
                    338: <sect4 id="before-anything">
                    339: <title>Before you do anything with htdocs:</title>
                    340: <orderedlist>
1.5       jschauma  341: <listitem>Ensure you have <pkg>lang/perl5</pkg> installed for the <ulink url="#dotlist-files">.list
                    342:     files</ulink>.  Also, see <ulink url="#what-is-required">above</ulink>.</listitem>
1.1       jschauma  343: <listitem>Check out <code>htdocs</code> from the CVS repository.</listitem>
                    344: <listitem>If you already have a copy of htdocs in your tree, make sure you update it
                    345: regularly.  In particular, when adding news items, make sure that
                    346: gallery/events.* is up to date as well, as the events are pulled in from
1.5       jschauma  347: there!  This is best done by running
                    348: <programlisting>
                    349:   $ cd htdocs
                    350:   $ make update</programlisting>
                    351: </listitem>
1.1       jschauma  352: </orderedlist>
                    353: </sect4>
                    354: 
                    355: <sect4 id="change-entry">
                    356: <title>To add a change entry:</title>
                    357: <orderedlist>
1.5       jschauma  358: <listitem>Edit htdocs/Changes/index.xml</listitem>
                    359: <listitem>Add a line in the TOC of the form
                    360: <programlisting>
                    361:   &lt;listitem&gt;&lt;ulink url="#link-name"&gt;XX Mon XXX - FREEFORM TITLE&lt;/ulink&gt;&lt;/listitem&gt;</programlisting>
1.1       jschauma  362: </listitem>
1.5       jschauma  363: <listitem>Further below, in the right section, add the actual entry of the
                    364: form
                    365:   <programlisting>
                    366:   &lt;sect3 id="link-name&gt;
                    367:   &lt;title&gt;XX Mon XXX - FREEFORM TITLE (&lt;ulink url="#monXXXX"&gt;top&lt;/ulink&gt;)&lt;/title&gt;
                    368:   &lt;para&gt;
                    369:     Entry text goes here.  Manual pages can be refered to as <quote>&amp;man.command.X;</quote>,
                    370:     email addresses as &lt;email&gt;full@address&lt;/email&gt;.
                    371:   &lt;para&gt;
                    372:   &lt;/sect3&gt;</programlisting>
                    373:   </listitem>
1.1       jschauma  374: <listitem>Run '<code>make</code>'</listitem>
                    375: </orderedlist>
1.5       jschauma  376: <para>
                    377: (The www team is working on simplifying this by automating the TOC
                    378: generation.)
                    379: </para>
1.1       jschauma  380: </sect4>
                    381: 
                    382: <sect4 id="adding-links">
                    383: <title>Adding links from the main pages:</title>
                    384: <para>
                    385: By running <code>make</code> from within htdocs/Changes, you will automatically 
                    386: update <ulink url="../">htdocs/index.html</ulink> and the index pages of all supported
                    387: translations.  No further action on your part is required.
                    388: </para>
                    389: <para>
                    390: Alternatively, you can run <code>make index</code> from the htdocs toplevel
                    391: directory.
                    392: </para>
                    393: </sect4>
                    394: 
                    395: <sect4 id="link-specific">
                    396: <title>If you want to add a link from a port specific page:</title>
                    397: <orderedlist>
                    398: <listitem>Edit htdocs/Ports/<emphasis>arch</emphasis>/index.html, and search for the
                    399:     '&lt;!-- news --&gt;' block.</listitem>
                    400: <listitem>Add a new entry to the subsequent list in the form:
                    401: <para>
                    402: <programlisting>&lt;dt&gt;&lt;b&gt;<emphasis>date</emphasis>:&lt;/b&gt; <emphasis>title</emphasis>
                    403:     &lt;dd&gt;<emphasis>body of item</emphasis>
                    404:     &lt;p&gt;</programlisting>
                    405: </para>
                    406:     where
                    407:     <itemizedlist>
                    408:     <listitem><emphasis>date</emphasis> - Normally as YEAR.MONTH.DATE</listitem>
                    409:     <listitem><emphasis>title</emphasis> - Freeform (short) text title</listitem>
                    410:     <listitem><emphasis>body of item</emphasis> - Freeform text for the entry. Can span mutltiple
                    411:        lines and may use HTML tags and links.</listitem>
                    412:     </itemizedlist>
                    413: </listitem>
                    414: </orderedlist>
                    415: </sect4>
                    416: 
                    417: <sect4 id="finally">
                    418: <title>Finally:</title>
                    419: <orderedlist>
                    420: <listitem>You may want to <ulink url="#validate-html">validate the HTML</ulink> in
                    421:     your modified files.</listitem>
                    422: <listitem>Check in the files - do not forget any <code>.list</code> files will
                    423:     update the matching <code>.html</code>.  The command 'make commit', when
                    424:        issued from the htdocs toplevel directory, will commit the main
                    425:        index-page, Changes/index.* and all the translations index pages with
                    426:        a default message of "NEWS; regen".  If you would like to add a more
                    427:        specific message, use 'MSG="Added News regarding FooBar" make
                    428:        commit'.</listitem>
                    429: <listitem>If the news is noteworthy it is a good idea to submit it to some news
                    430:     sites, like 
                    431:     <ulink url="http://daily.daemonnews.org/add_story.php3">Daily Daemonnews</ulink>,
                    432:     <ulink url="http://www.osnews.com/submit.php">OSNews</ulink>,
                    433:     <ulink url="http://slashdot.org/submit.pl">Slashdot</ulink>,
                    434:     <ulink url="http://www.newsforge.com/submit.pl">Newsforge</ulink> and
                    435:     <ulink url="http://www.bsdforums.org/submitnews.php">BSDForums</ulink>.</listitem>
                    436: </orderedlist>
                    437: </sect4>
                    438: 
                    439: </sect3>
                    440: 
                    441: <sect3 id="adding-events">
                    442: <title>Adding Events</title>
                    443: <para>
                    444: The main index page also contains links to "Upcoming Events".  These links are
                    445: updated much like the <ulink url="#adding-news-items">News entries</ulink>:
                    446: </para>
                    447: <para>
                    448:   <programlisting>
                    449: cd .../htdocs/gallery
1.5       jschauma  450: $EDITOR events.xml
1.1       jschauma  451: make events</programlisting>
                    452: </para>
                    453: 
                    454: <para>
                    455: Since the events are included on all the translations index pages, all these
                    456: pages need to be generated and committed as well.  This can be achieved by
                    457: issuing the 'make index' command from the htdocs directory.    
                    458: </para>
                    459: <para>
                    460:   <programlisting>
                    461: cd .../htdocs
                    462: make index
                    463: MSG="Added Event Foo" make commit</programlisting>
                    464: </para>
                    465: </sect3>
                    466: 
                    467: <sect3 id="adding-mailinglists">
                    468: <title>Adding to/editing the MailingLists page </title>
                    469: <para>
                    470: If a mailing-list is missing from the
                    471: <ulink url="../MailingLists/">MailingLists</ulink> page:
                    472: <orderedlist>
                    473: <listitem>Edit the htdocs/MailingLists/index.m4 file</listitem>
                    474: <listitem>Run the makefile in htdocs/MailingLists, it will generate the index.html</listitem>
                    475: <listitem>Confirm the generated html is good.</listitem>
                    476: <listitem>commit the index.m4 and index.html files.</listitem>
                    477: </orderedlist>
                    478: </para>
                    479: </sect3>
                    480: 
                    481: <sect3 id="consultants">
                    482: <title>Consultants for hire</title>
                    483: <para>
                    484: Before adding an entry to the ``Consultants for hire'' page (<ulink
                    485: url="../gallery/consultants.html">gallery/consultants.html</ulink>), please ask
                    486: that the person in question provides a link back to our homepage and/or
                    487: mentions NetBSD on their website.  Needless to say that you should make sure
                    488: that the URL given is active and accessible.
                    489: </para>
                    490: 
                    491: </sect3>
                    492: </sect2>
                    493: </sect1>
                    494: </webpage>

CVSweb <webmaster@jp.NetBSD.org>