Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: website apache clerezza
From: Henry Story <henry.story@bblfish.net>
In-Reply-To: <AANLkTi=YUMsEpTcGrqPWc9ygWW6fge_0Sayi2uM2+0ur@mail.gmail.com>
Date: Thu, 17 Mar 2011 16:34:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DF0C912-726F-411D-89A6-D32724358338@bblfish.net>
References: <AANLkTi=NR5yVH9bpygt1Tr87_bWn8V-DZ2KjtxACtWia@mail.gmail.com>
 <AANLkTikatHpfEngL53gvXkNkXTg+VU12qFmp6v-qd75p@mail.gmail.com>
 <5863FB4055D90542A7A7DAE0CEF2ACB0064F8ABB00@E2K7CCR1.netvigour.com>
 <4D811D68.9070007@apache.org>
 <AANLkTi=_uFjKZ+ab50v=TB5OcDbKbBZFjMYsLivmtY9W@mail.gmail.com>
 <AANLkTinic7n9TmJ3ewfqOECfHT99yGiwd6M7_QfN+sm1@mail.gmail.com>
 <AANLkTikrG4uJZJH=dZPo-pZjvEO46JBUZVNJX39x0M-9@mail.gmail.com>
 <AANLkTi=-VQkU8D+iV0Y6FQ56N5sy0zm6sHZWOex+cuUa@mail.gmail.com>
 <AANLkTi=Cw0J0hO0TJZSE6tTXQ7vbVAqCCA8_eOmrrmAA@mail.gmail.com>
 <389F2F67-9883-407C-A974-5B13A3038446@bblfish.net>
 <AANLkTi=QpWB0HS6Y7MfW8CyC5uQg9yQLtLcxsGGU0-oN@mail.gmail.com>
 <AANLkTi=YUMsEpTcGrqPWc9ygWW6fge_0Sayi2uM2+0ur@mail.gmail.com>
To: clerezza-dev@incubator.apache.org

Hi all,

  Having the web site site https://incubator.apache.org/clerezza/ look =
good on first access
is really important, especially as I am telling everyone how interesting =
a project this is.

  So in my view it does not matter at all how this is done, as long as =
it looks good, the documentation is available there immediately, it is =
stable, and nobody can kill the server.

  Then the really interesting part is to see how the process can be =
guided by the pure html crowd. As far as possible those devs should have =
need to no tools other than an editor (vi is a must*) and a bunch of =
browsers. No JSPs, not complex language to learn. Perhaps server side =
includes are allowed. HTML and aesthetics are two fields that are =
complex enough to learn for anyone.

  How far can they go with the above, without this work getting tedious =
for them?
 =20
  For the documentation, my guess is that that's all that is needed. For =
more dynamic sites one would like to be able to get going from that =
somehow. But the burden should be on the code to fetch real working =
templates, cut them into pieces and display them dynamically.

  Then the interesting bit is how can the semweb make things simpler. =
Perhaps one can just describe a page as a bunch of templates, =
distributed around the web? One simple rdf file that points to a bunch =
of places, a server that fetches those and builds the views?

Currently the documentation is here I am finding out

  - http://localhost:8080/documentation/
  - =
https://svn.apache.org/repos/asf/incubator/clerezza/site/trunk/readme.txt

I'll look at that in more detail as soon as I fixed some issues in the =
code I am working on.=20

It should not matter in the end how documentation is written. The page =
for a component can have a seealso link to the mvn component for =
example. As long as the pieces are cleanly seperatable and nameable.

 Clerezza is not in my view mostly a CMS. It's much bigger than that: =
it's a key piece of the distributed social web. If it were just a CMS it =
would not be interesting: there are thousands of those already. The =
semantic web piece is interesting because it should allow us to get us =
all to collaborate a lot more easily.

   Just my 2 cents.

	Henry

* ;-) just trying to start an old religious war here. No Dreamweaver is =
what people at AltaVista used 10 years ago. I think they still do.=