On 11 May 2001, at 18:17, Frank Schlottmann-Goedde wrote:
> > 3) Each audience should easy find its way to their area of interest.
> > Thus idea of portal-like site with levelled down sections obviously
> > come to mind. We can also split it to more independent sites (at
> > least to two for newcomers and users&developers as was proposed
> > by Markus). I prefer the first solution, despite that a lot of work
> > would be needed to twist phpNuke.
> I don't know how phpNuke works, but wouldn't it be possible to create
> a (simple) front page that leads to either this phpNuke stuff or
> to the newcomers links? (Something like the previous rabbit holes?)
Technically, it should be possible, but I'm not sure what gain we
would get from this. We can also directly twist phpNuke (the code
that generate the front page) that way.
> > 4) Site maintenance has two areas: site design&development and
> > content management.
> Anyone who ever dared to visit my homepage will know, that this
> design stuff don't have any priority for me.
> Content is a question of available time. (I usually don't have any)
That is. There are people who love to polish the site layout, and
others who'd like edit content only. They should be able to work
separately and don't care about other group. Of course, they
should make an arrangement about site and information structure
(that should be enough).
> > 5) Automation gimmicks and other features of dynamic site should
> > be also considered. I think that we could utilize at least some, like
> > polls, automatically generated statistics etc. We already have
> > some at SourceForge and it would be nice if we would be able to
> > integrate them into our site.
> The structure is there, so let's use it.
Unfortunately, the database and php code that drive our
SourceForge facilities is on another server (and database is
PostgreSQL). Direct integration would require cooperation with SF
staff (but it should be great improvement that many SF hosted
projects can use).