From owner-freebsd-www  Thu Feb 27 02:50:26 1997
Return-Path: <owner-freebsd-www>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA18220
          for www-outgoing; Thu, 27 Feb 1997 02:50:26 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18214
          for <webmaster@freefall.freebsd.org>; Thu, 27 Feb 1997 02:50:22 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id CAA11147; Thu, 27 Feb 1997 02:50:03 -0800 (PST)
To: Doug White <dwhite@resnet.uoregon.edu>
cc: "Joe \"Marcus\" Clarke" <jmcla@ocala.cs.miami.edu>,
        webmaster@freefall.freebsd.org
Subject: Re: New ports 
In-reply-to: Your message of "Wed, 26 Feb 1997 19:48:14 PST."
             <Pine.BSI.3.94.970226194603.8482T-100000@localhost> 
Date: Thu, 27 Feb 1997 02:50:03 -0800
Message-ID: <11143.857040603@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-www@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> The ports tree changes too fast on a daily basis to flag the changes in
> the www heirarchy (although our esteemed webmasters may have a different
> opinion).  

I think a "what's new" page is definitely a reasonable thing, though
making it for the ports collection alone might be less powerful than
simply building an idea of "newness" into the web page build process
itself.  At the very end of the build, those files which were newer
than the others would be assumed to be changed somehow and an special
"what's new" index built as the very last thing done.  Perhaps you
could search for <label> tags in each changed file and build a list of
new references that way, I dunno.

As our docset grows, having some way to quickly index it by date
or content does seem a very reasonable goal.

						Jordan