Reed Shadgett wrote:
> I think I got all the ones people have said.  If I missed any, it's
> not that I don't agree with them, it's that I likely forgot.

I assume that people's comments were about all the port pages in general
and not the mac68k page specifically, right?  ;-)
 
> There's only one non-compliant part, which is the block-inline crap
> in the news portion.  While this could be easily fixed now, it'd add
> extra work for syncing news.html (stripping tags and the such).
> 
> It'll get fixed when we move news entries to a separate file and have
> the relevant portion of index.html and news.html generated from that
> (similar to our list magic).
> 
> Actually, I'd probably want news entries to be added to news.html,
> and have the relevant portion of index.html generated.  Though I've
> heard mutterings of all news entries in one file (to concentrate
> the portion of the site that changes the most - to make it easier
> on translaters)... I'm open to that.

there is 1 advantage to not having the news auto-generated, and that is
that we are currently keeping the more relevant news items rather than
having them all scroll off.  with the mac68k port, we get a new -current
snapshot every week or so.  these items will quickly overwhelm other
perhaps more interesting items like the latest full release or new device
support.  perhaps we need a "latest snapshot" permanent news item or
something like that?

> > The _new_ new port page?
> 
> Feedback please.  We _are_ trying to please as large a percentage as
> possible here. :) 

on the whole, i like it.  the directory portion does look vaguely
unbalanced as there are headings for everything except for the FAQ
pointers.  perhaps this could be categorized, too?  not that i have any
useful suggestions for a name...

anyway, great work!

-colin