Re: [Cscene-discuss] Look and Feel

[<j....@t-...>]

On Tue, 4 Jan 2000 19:52:17 -0600, ixx wrote:

>This is what I was wanting.  Just not for mirrors.  The backend and/or main
>site.  Then have the ability for static mirroring.

Whatever technology you use, you can always "wget -r localhost" and
create a static image.

>i do not know how new articles would come in.. direct to cvs?  then editors
>play there?  anyhow all sounds good.  dynamic backend and static frontend.

One possible way is this: add the article somewhere in the article tree
(the organization of which is to be discussed), then add a new line to
the article database (let's assume this is a text or XML file, so
that's easily done with CVS). A state change (REVIEW -> ACK) is then
also done via CVS.

On the article tree: I think .../articles/<author>/foo.html (foo.xml)
would be the way to go, so each author can maintain his own stuff. Or
if only editors get CVS access, articles/<editor>/...

If each author/editor has his own area, naming issues become obsolete,
the repository is organized, and each author can create subtrees (for
code archives or whatever). 

>I have not played with xml much, but i be glad to provide perl coding, and
>learn xml on the way :)

I have Cocoon running locally on a Win/NT and Apache basis, it's
extremely nice. Much of XML technology is Java, but C++ and Perl can be
used also, _especially_ for batch processing. Take a look at
xml.apache.org, it's a dynamic XML site based on Cocoon.

>probably the easiest would be to search via the main cscene site and rewrite
>the urls appropriately.

Sure. That should be the default, and power-mirrors can add a local
search.

Ciao, Jürgen