Re: [Cscene-discuss] Look and Feel

[ixx <ix...@cs...>]

On Wed, Jan 05, 2000 at 04:21:42AM +0100, Juergen Hermann wrote:
> On Tue, 4 Jan 2000 19:52:17 -0600, ixx wrote:
> >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 do not know if authors will have cvs access.  because who knows who will be
an author right?  i want anyone to be able to submit an article.  maybe i will
setup something for authors to work out of.  anyhow i imagine only editors and
web admin ppl will have cvs access.

we need a spot for preview too.  will that be straight from CVS or a export
into HTML on a preview site?

> >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.
 
OK.  but i do not think we should require XML from authors.