You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by Tsuyoshi Ito <ts...@trialox.org> on 2011/03/16 17:08:41 UTC
website apache clerezza
Hi
I am working on the html prototype of the clerezza website. I want to
ask if somebody knows if there are any best practices on how to
deploy/maintain an apache website (xsite?). IMO most of the website
content is static and therefore does not have to be created
dynamically. Probably we have a news section and a download section
which should be generated dynamically (via continuous integration
server) or feeded from our demo server.
However a first prototype is available under
https://incubator.apache.org/clerezza/spike/
feedback is welcome (https://issues.apache.org/jira/browse/CLEREZZA-448)
cheers
tsuy
Re: website apache clerezza
Posted by Henry Story <he...@bblfish.net>.
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?
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.
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.
Re: website apache clerezza
Posted by Reto Bachmann-Gmuer <re...@trialox.org>.
Hi Tsuy
I'm happy to support you if you encounter problems with the current process,
this might also help improving the process.
Also with the current process it is possible to include static files, also
things get simpler thanks to CLEREZZA-INF/web-resources which causes static
files provided by bundles to be included in the offline site.
If you have architectural document you failed you publish I can add them for
you. I could also try doing an instructional video out of the process of
adding it :)
Just for the current discussion of changing the publishing process, I think
never reported problems (as well as the typo first reported in Marco's
recent mail) are very weak arguments.
Reto
On Thu, Mar 17, 2011 at 1:38 PM, Tsuyoshi Ito <ts...@trialox.org> wrote:
> Hi
>
> I had 2 problems in the past to update the current apache clerezza site:
> 1. only reto had write permission => this is fixed (INFRA-3477)
> 2. the process to update the website was too complicated for me ( I
> tried to add an archticture documentation: CLEREZZA-334)
>
> IMO having a website with useful information for [potential] users
> should be the focus right now. Furthermore it should be easy to update
> for ever committer (also users who are not committers but want to
> contribute to the content of the website should be able to deliver a
> patch.
>
> But I think we should discuss solutions for the future, which should
> be clerezza based (as suggested by Henry or it is also possible to
> use trialox cms components)
>
> I have had a quick look into Apache CMS and think this is a way to go.
> Or storing the website content directly in the svn repository is also
> solution in the short term for me.
>
> Cheers
> Tsuy
>
> On Thu, Mar 17, 2011 at 12:56 PM, Henry Story <he...@bblfish.net>
> wrote:
> >
> > On 17 Mar 2011, at 11:49, Reto Bachmann-Gmuer wrote:
> >
> >>
> >> If in another half a year we see that even after having repeatedly
> updated
> >> the site it still takes unbearable extra-time to perform an update then
> we
> >> should reconsider changing the process. Apache CMS might be an
> alternative,
> >> static html files hardly are.
> >
> > This is a bit above my knowledge here, but I'd suggest that static pages
> are excellent
> > for documentation, and that is what is perhaps most needed for new
> developers to
> > come along. The backend logic for that is so simple, it could easily be
> done
> > in a wiki even. Once done it can always be slurped into Clerezza and
> republished
> > there it seems to me. It could even be a useful module to have: if Apache
> is used
> > to publishing sites a certain way, then a module that used input
> generated that way,
> > with a bit of rdfa markup perhaps, would make for an easy transition.
> >
> > The pages here
> >
> > https://incubator.apache.org/clerezza/spike/
> >
> > look very good.
> >
> > We should at some point develop a module where html developers need to
> know nothing
> > at all about clerezza in order to generate templates that they can use.
> This is the
> > thinking that led to projects such as
> >
> > - Enhydra XMLC [1] (2000->)
> > - apache wicket [2]
> > - lift scala library [3]
> >
> > What would be useful would be to tune the experience gained form those
> and see how the semantic web could add a further improvement to them.
> >
> > But in any case if html devs want to make beautiful pages, the experience
> of those frameworks is that what they produce has to be html.
> >
> > Henry
> >
> >
> > [1] http://xmlc.ow2.org/doc/index.html
> > [2] http://wicket.apache.org/
> > [3] http://demo.liftweb.net/templating/
> > Henry
> >
> >
> > Social Web Architect
> > http://bblfish.net/
> >
> >
>
Re: website apache clerezza
Posted by Tsuyoshi Ito <ts...@trialox.org>.
Hi
I had 2 problems in the past to update the current apache clerezza site:
1. only reto had write permission => this is fixed (INFRA-3477)
2. the process to update the website was too complicated for me ( I
tried to add an archticture documentation: CLEREZZA-334)
IMO having a website with useful information for [potential] users
should be the focus right now. Furthermore it should be easy to update
for ever committer (also users who are not committers but want to
contribute to the content of the website should be able to deliver a
patch.
But I think we should discuss solutions for the future, which should
be clerezza based (as suggested by Henry or it is also possible to
use trialox cms components)
I have had a quick look into Apache CMS and think this is a way to go.
Or storing the website content directly in the svn repository is also
solution in the short term for me.
Cheers
Tsuy
On Thu, Mar 17, 2011 at 12:56 PM, Henry Story <he...@bblfish.net> wrote:
>
> On 17 Mar 2011, at 11:49, Reto Bachmann-Gmuer wrote:
>
>>
>> If in another half a year we see that even after having repeatedly updated
>> the site it still takes unbearable extra-time to perform an update then we
>> should reconsider changing the process. Apache CMS might be an alternative,
>> static html files hardly are.
>
> This is a bit above my knowledge here, but I'd suggest that static pages are excellent
> for documentation, and that is what is perhaps most needed for new developers to
> come along. The backend logic for that is so simple, it could easily be done
> in a wiki even. Once done it can always be slurped into Clerezza and republished
> there it seems to me. It could even be a useful module to have: if Apache is used
> to publishing sites a certain way, then a module that used input generated that way,
> with a bit of rdfa markup perhaps, would make for an easy transition.
>
> The pages here
>
> https://incubator.apache.org/clerezza/spike/
>
> look very good.
>
> We should at some point develop a module where html developers need to know nothing
> at all about clerezza in order to generate templates that they can use. This is the
> thinking that led to projects such as
>
> - Enhydra XMLC [1] (2000->)
> - apache wicket [2]
> - lift scala library [3]
>
> What would be useful would be to tune the experience gained form those and see how the semantic web could add a further improvement to them.
>
> But in any case if html devs want to make beautiful pages, the experience of those frameworks is that what they produce has to be html.
>
> Henry
>
>
> [1] http://xmlc.ow2.org/doc/index.html
> [2] http://wicket.apache.org/
> [3] http://demo.liftweb.net/templating/
> Henry
>
>
> Social Web Architect
> http://bblfish.net/
>
>
RE: website apache clerezza
Posted by Marco Zaugg <ma...@getunik.com>.
+1 to Henry's, Tommaso's and Tsuy's post. Let's go with
static html files and use Clerezza in a second step.
Every additional day the current site is up and running
is a lost day as we simply do not attract new developers
to join.
-----Original Message-----
From: Henry Story [mailto:henry.story@bblfish.net]
Sent: Donnerstag, 17. März 2011 12:57
To: clerezza-dev@incubator.apache.org
Cc: Tommaso Teofili
Subject: Re: website apache clerezza
On 17 Mar 2011, at 11:49, Reto Bachmann-Gmuer wrote:
>
> If in another half a year we see that even after having repeatedly updated
> the site it still takes unbearable extra-time to perform an update then we
> should reconsider changing the process. Apache CMS might be an alternative,
> static html files hardly are.
This is a bit above my knowledge here, but I'd suggest that static pages are excellent
for documentation, and that is what is perhaps most needed for new developers to
come along. The backend logic for that is so simple, it could easily be done
in a wiki even. Once done it can always be slurped into Clerezza and republished
there it seems to me. It could even be a useful module to have: if Apache is used
to publishing sites a certain way, then a module that used input generated that way,
with a bit of rdfa markup perhaps, would make for an easy transition.
The pages here
https://incubator.apache.org/clerezza/spike/
look very good.
We should at some point develop a module where html developers need to know nothing
at all about clerezza in order to generate templates that they can use. This is the
thinking that led to projects such as
- Enhydra XMLC [1] (2000->)
- apache wicket [2]
- lift scala library [3]
What would be useful would be to tune the experience gained form those and see how the semantic web could add a further improvement to them.
But in any case if html devs want to make beautiful pages, the experience of those frameworks is that what they produce has to be html.
Henry
[1] http://xmlc.ow2.org/doc/index.html
[2] http://wicket.apache.org/
[3] http://demo.liftweb.net/templating/
Henry
Social Web Architect
http://bblfish.net/
Re: website apache clerezza
Posted by Henry Story <he...@bblfish.net>.
On 17 Mar 2011, at 11:49, Reto Bachmann-Gmuer wrote:
>
> If in another half a year we see that even after having repeatedly updated
> the site it still takes unbearable extra-time to perform an update then we
> should reconsider changing the process. Apache CMS might be an alternative,
> static html files hardly are.
This is a bit above my knowledge here, but I'd suggest that static pages are excellent
for documentation, and that is what is perhaps most needed for new developers to
come along. The backend logic for that is so simple, it could easily be done
in a wiki even. Once done it can always be slurped into Clerezza and republished
there it seems to me. It could even be a useful module to have: if Apache is used
to publishing sites a certain way, then a module that used input generated that way,
with a bit of rdfa markup perhaps, would make for an easy transition.
The pages here
https://incubator.apache.org/clerezza/spike/
look very good.
We should at some point develop a module where html developers need to know nothing
at all about clerezza in order to generate templates that they can use. This is the
thinking that led to projects such as
- Enhydra XMLC [1] (2000->)
- apache wicket [2]
- lift scala library [3]
What would be useful would be to tune the experience gained form those and see how the semantic web could add a further improvement to them.
But in any case if html devs want to make beautiful pages, the experience of those frameworks is that what they produce has to be html.
Henry
[1] http://xmlc.ow2.org/doc/index.html
[2] http://wicket.apache.org/
[3] http://demo.liftweb.net/templating/
Henry
Social Web Architect
http://bblfish.net/
Re: website apache clerezza
Posted by Reto Bachmann-Gmuer <re...@trialox.org>.
Hi Tommaso and all,
I'm not sure if our bsd jail would actually be powerful enough to server
concurrent requests quickly enough, I haven't had enough time yet to play to
see how to best set it up but the first attempts looked rather
disappointing.
I think the obvious flaws of the current site are not a reason not to
proceed iteratively. Having a prototype is good to know in which direction
we want to go, now we should improve the actual site. I reckon the process
for publishing the site offers room for improvement, I think this
improvements will arise when we actually use it. In the process of using it
we will also learn about Clerezza from the user perspective. We will create
templates that we can use both on the site and on demo instances and that
might also show as how we can best improve (CLEREZZA-147) the default css
and renderlets.
I very much appreciate the fact, that now others are caring about the site
as well. I understand the wish to have the ideas of the prototype quickly,
however I think that after half a year of little activity (8 revisions all
by me) we must not fall into a blind activism. Our site shall be easy to
maintain so that it allows up-to-date information. Compromises on the
easiness of maintainability are only justifiable if they help us improve
Clerezza (as it already did by showing bugs in the stable serializer).
I think creating a style for Clerezza based on the design concepts in the
prototype would be the best next step. If we can use components of the
trialox CMS to make the editing easier (and closer to wysiwyg) that would be
great as well, but I find it a bit strange that after half a year that
nobody actually tried improving the site (concluding this from the lack of
commits or posts/issues describing failures) we should conclude that the
current process isn't practicable.
If in another half a year we see that even after having repeatedly updated
the site it still takes unbearable extra-time to perform an update then we
should reconsider changing the process. Apache CMS might be an alternative,
static html files hardly are.
Reto
On Thu, Mar 17, 2011 at 10:35 AM, Tommaso Teofili <tommaso.teofili@gmail.com
> wrote:
> Hi all,
> at first I thought the best solution was to eat our own dogfood, like Reto
> said, then I realized we have a dedicated zone for Clerezza which can be
> good to demonstrate its capabilities.
> So now I think the best idea is going on with Apache CMS to quickly deliver
> our website, and of course provide pointers to our Clerezza zone to let
> people "have a look" at Clerezza.
> By the way, I like Tsuy's prototype.
> Cheers,
> Tommaso
>
> 2011/3/17 Tsuyoshi Ito <ts...@trialox.org>
>
> > hi
> >
> > i think using apache clerezza to generate our website a good idea but
> > i also think in the ASF context this not possible without a lot of
> > overhead:
> >
> > currently the following steps have to be done
> >
> > 1. load content from the svn repo into a apache clerezza instance
> > (access or own instance needed)
> >
> > 2. edit content in a rudimentar html editor (not wysiwyg)
> >
> > 3. export content with a clerezza tool => generate html files etc.
> >
> > 4. rdf data and html files have to be updated in the svn repo.
> >
> > 5. page has to be published to apache.org server
> >
> > There is no real benefit having content as rdf right know - so I don't
> > see why we should do the extra steps.
> >
> > storing website content directly in svn repo seem to be easier to
> > maintain (step 1 & 3 are obsolete)
> >
> > cheers
> > tsuy
> >
> > On Wed, Mar 16, 2011 at 10:22 PM, Bertrand Delacretaz
> > <bd...@apache.org> wrote:
> > > On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer
> > > <re...@trialox.org> wrote:
> > >> Currently in svn we store data from which the whole website can be
> > generated
> > >> (by using clerezza) but not the generated files. Should we add them to
> > SVN
> > >> as well?..
> > >
> > > Yes, if the website content is available in svn that's fine.
> > >
> > > Svnpubsub [1] can the be setup by ASF infra for near-instant
> > > publishing of updates when they are committed to clerezza's svn.
> > >
> > > -Bertrand
> > >
> > > [1]
> >
> http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
> > > (dunno if there are other docs)
> > >
> >
>
Re: website apache clerezza
Posted by Tommaso Teofili <to...@gmail.com>.
Hi all,
at first I thought the best solution was to eat our own dogfood, like Reto
said, then I realized we have a dedicated zone for Clerezza which can be
good to demonstrate its capabilities.
So now I think the best idea is going on with Apache CMS to quickly deliver
our website, and of course provide pointers to our Clerezza zone to let
people "have a look" at Clerezza.
By the way, I like Tsuy's prototype.
Cheers,
Tommaso
2011/3/17 Tsuyoshi Ito <ts...@trialox.org>
> hi
>
> i think using apache clerezza to generate our website a good idea but
> i also think in the ASF context this not possible without a lot of
> overhead:
>
> currently the following steps have to be done
>
> 1. load content from the svn repo into a apache clerezza instance
> (access or own instance needed)
>
> 2. edit content in a rudimentar html editor (not wysiwyg)
>
> 3. export content with a clerezza tool => generate html files etc.
>
> 4. rdf data and html files have to be updated in the svn repo.
>
> 5. page has to be published to apache.org server
>
> There is no real benefit having content as rdf right know - so I don't
> see why we should do the extra steps.
>
> storing website content directly in svn repo seem to be easier to
> maintain (step 1 & 3 are obsolete)
>
> cheers
> tsuy
>
> On Wed, Mar 16, 2011 at 10:22 PM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
> > On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer
> > <re...@trialox.org> wrote:
> >> Currently in svn we store data from which the whole website can be
> generated
> >> (by using clerezza) but not the generated files. Should we add them to
> SVN
> >> as well?..
> >
> > Yes, if the website content is available in svn that's fine.
> >
> > Svnpubsub [1] can the be setup by ASF infra for near-instant
> > publishing of updates when they are committed to clerezza's svn.
> >
> > -Bertrand
> >
> > [1]
> http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
> > (dunno if there are other docs)
> >
>
Re: website apache clerezza
Posted by Hasan Hasan <ha...@trialox.org>.
hi all,
I am against putting too much effort to produce only a few pages which do
not change often. Let's concentrate on the content rather than on the way to
generate those pages. IMO it is enough to have some nice looking static
pages with high quality of content. The use of clerezza instance for this
task would require much effort than actually needed.
regards
hasan
On Thu, Mar 17, 2011 at 9:29 AM, Tsuyoshi Ito <ts...@trialox.org> wrote:
> hi
>
> i think using apache clerezza to generate our website a good idea but
> i also think in the ASF context this not possible without a lot of
> overhead:
>
> currently the following steps have to be done
>
> 1. load content from the svn repo into a apache clerezza instance
> (access or own instance needed)
>
> 2. edit content in a rudimentar html editor (not wysiwyg)
>
> 3. export content with a clerezza tool => generate html files etc.
>
> 4. rdf data and html files have to be updated in the svn repo.
>
> 5. page has to be published to apache.org server
>
> There is no real benefit having content as rdf right know - so I don't
> see why we should do the extra steps.
>
> storing website content directly in svn repo seem to be easier to
> maintain (step 1 & 3 are obsolete)
>
> cheers
> tsuy
>
> On Wed, Mar 16, 2011 at 10:22 PM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
> > On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer
> > <re...@trialox.org> wrote:
> >> Currently in svn we store data from which the whole website can be
> generated
> >> (by using clerezza) but not the generated files. Should we add them to
> SVN
> >> as well?..
> >
> > Yes, if the website content is available in svn that's fine.
> >
> > Svnpubsub [1] can the be setup by ASF infra for near-instant
> > publishing of updates when they are committed to clerezza's svn.
> >
> > -Bertrand
> >
> > [1]
> http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
> > (dunno if there are other docs)
> >
>
Re: website apache clerezza
Posted by Tsuyoshi Ito <ts...@trialox.org>.
hi
i think using apache clerezza to generate our website a good idea but
i also think in the ASF context this not possible without a lot of overhead:
currently the following steps have to be done
1. load content from the svn repo into a apache clerezza instance
(access or own instance needed)
2. edit content in a rudimentar html editor (not wysiwyg)
3. export content with a clerezza tool => generate html files etc.
4. rdf data and html files have to be updated in the svn repo.
5. page has to be published to apache.org server
There is no real benefit having content as rdf right know - so I don't
see why we should do the extra steps.
storing website content directly in svn repo seem to be easier to
maintain (step 1 & 3 are obsolete)
cheers
tsuy
On Wed, Mar 16, 2011 at 10:22 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer
> <re...@trialox.org> wrote:
>> Currently in svn we store data from which the whole website can be generated
>> (by using clerezza) but not the generated files. Should we add them to SVN
>> as well?..
>
> Yes, if the website content is available in svn that's fine.
>
> Svnpubsub [1] can the be setup by ASF infra for near-instant
> publishing of updates when they are committed to clerezza's svn.
>
> -Bertrand
>
> [1] http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
> (dunno if there are other docs)
>
Re: website apache clerezza
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer
<re...@trialox.org> wrote:
> Currently in svn we store data from which the whole website can be generated
> (by using clerezza) but not the generated files. Should we add them to SVN
> as well?..
Yes, if the website content is available in svn that's fine.
Svnpubsub [1] can the be setup by ASF infra for near-instant
publishing of updates when they are committed to clerezza's svn.
-Bertrand
[1] http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
(dunno if there are other docs)
Re: website apache clerezza
Posted by Reto Bachmann-Gmuer <re...@trialox.org>.
Currently in svn we store data from which the whole website can be generated
(by using clerezza) but not the generated files. Should we add them to SVN
as well?
Reto
On Wed, Mar 16, 2011 at 9:28 PM, Ross Gardler <rg...@apache.org> wrote:
> Just be warned that the ASF infrastructure team do not support a wide range
> of solutions for managing Apache websites. The main reason is that they have
> to make sure our servers stay up and running and you'd be surprised at the
> load placed on them and the security requirements we have.
>
> The basic rule is that the content must be statically served from ASF
> servers and that content must be placed in SVN to allow infra to do their
> "magic".
>
> The ASF provides simple CMS system for creating websites. I'd describe this
> as bare bones, but functional. It allows for online and offline (via
> subversion) editing. There are also a number of tools for generating the
> static content from other sources.
>
> When it comes time to consider the publication chain your mentors will tell
> you more.
>
> Ross
>
>
>
> On 16/03/2011 19:53, Marco Zaugg wrote:
>
>> Good idea. We could even go using the open-sourced web content management
>> system
>> 'Trialox CMS' which is based on Apache Clerezza.
>>
>> But I'd suggest to first focus on the content of the website instead of
>> spending
>> too much time in create the pages dynamically. The current site on
>> http://incubator.apache.org/clerezza/
>> is simply too bad (and it's still having this nasty typo at the beginning
>> of the
>> page 'ApachClerezza').
>>
>> -----Original Message-----
>> From: reto@trialox.org [mailto:reto@trialox.org] On Behalf Of Reto
>> Bachmann-Gmuer
>> Sent: Mittwoch, 16. März 2011 20:44
>> To: clerezza-dev@incubator.apache.org
>> Cc: Tsuyoshi Ito; Dirk Dresch
>> Subject: Re: website apache clerezza
>>
>> Hi Tsuy
>>
>> I see no reason not to eat our own dogfood and create the website using
>> Clerezza as we're currently doing.
>>
>> Reto
>>
>> On Wed, Mar 16, 2011 at 5:08 PM, Tsuyoshi Ito<ts...@trialox.org>
>> wrote:
>>
>> Hi
>>>
>>> I am working on the html prototype of the clerezza website. I want to
>>> ask if somebody knows if there are any best practices on how to
>>> deploy/maintain an apache website (xsite?). IMO most of the website
>>> content is static and therefore does not have to be created
>>> dynamically. Probably we have a news section and a download section
>>> which should be generated dynamically (via continuous integration
>>> server) or feeded from our demo server.
>>>
>>> However a first prototype is available under
>>> https://incubator.apache.org/clerezza/spike/
>>>
>>> feedback is welcome (https://issues.apache.org/jira/browse/CLEREZZA-448)
>>>
>>> cheers
>>> tsuy
>>>
>>>
>
Re: website apache clerezza
Posted by Ross Gardler <rg...@apache.org>.
Just be warned that the ASF infrastructure team do not support a wide
range of solutions for managing Apache websites. The main reason is that
they have to make sure our servers stay up and running and you'd be
surprised at the load placed on them and the security requirements we have.
The basic rule is that the content must be statically served from ASF
servers and that content must be placed in SVN to allow infra to do
their "magic".
The ASF provides simple CMS system for creating websites. I'd describe
this as bare bones, but functional. It allows for online and offline
(via subversion) editing. There are also a number of tools for
generating the static content from other sources.
When it comes time to consider the publication chain your mentors will
tell you more.
Ross
On 16/03/2011 19:53, Marco Zaugg wrote:
> Good idea. We could even go using the open-sourced web content management system
> 'Trialox CMS' which is based on Apache Clerezza.
>
> But I'd suggest to first focus on the content of the website instead of spending
> too much time in create the pages dynamically. The current site on http://incubator.apache.org/clerezza/
> is simply too bad (and it's still having this nasty typo at the beginning of the
> page 'ApachClerezza').
>
> -----Original Message-----
> From: reto@trialox.org [mailto:reto@trialox.org] On Behalf Of Reto Bachmann-Gmuer
> Sent: Mittwoch, 16. März 2011 20:44
> To: clerezza-dev@incubator.apache.org
> Cc: Tsuyoshi Ito; Dirk Dresch
> Subject: Re: website apache clerezza
>
> Hi Tsuy
>
> I see no reason not to eat our own dogfood and create the website using
> Clerezza as we're currently doing.
>
> Reto
>
> On Wed, Mar 16, 2011 at 5:08 PM, Tsuyoshi Ito<ts...@trialox.org> wrote:
>
>> Hi
>>
>> I am working on the html prototype of the clerezza website. I want to
>> ask if somebody knows if there are any best practices on how to
>> deploy/maintain an apache website (xsite?). IMO most of the website
>> content is static and therefore does not have to be created
>> dynamically. Probably we have a news section and a download section
>> which should be generated dynamically (via continuous integration
>> server) or feeded from our demo server.
>>
>> However a first prototype is available under
>> https://incubator.apache.org/clerezza/spike/
>>
>> feedback is welcome (https://issues.apache.org/jira/browse/CLEREZZA-448)
>>
>> cheers
>> tsuy
>>
RE: website apache clerezza
Posted by Marco Zaugg <ma...@getunik.com>.
Good idea. We could even go using the open-sourced web content management system
'Trialox CMS' which is based on Apache Clerezza.
But I'd suggest to first focus on the content of the website instead of spending
too much time in create the pages dynamically. The current site on http://incubator.apache.org/clerezza/
is simply too bad (and it's still having this nasty typo at the beginning of the
page 'ApachClerezza').
-----Original Message-----
From: reto@trialox.org [mailto:reto@trialox.org] On Behalf Of Reto Bachmann-Gmuer
Sent: Mittwoch, 16. März 2011 20:44
To: clerezza-dev@incubator.apache.org
Cc: Tsuyoshi Ito; Dirk Dresch
Subject: Re: website apache clerezza
Hi Tsuy
I see no reason not to eat our own dogfood and create the website using
Clerezza as we're currently doing.
Reto
On Wed, Mar 16, 2011 at 5:08 PM, Tsuyoshi Ito <ts...@trialox.org> wrote:
> Hi
>
> I am working on the html prototype of the clerezza website. I want to
> ask if somebody knows if there are any best practices on how to
> deploy/maintain an apache website (xsite?). IMO most of the website
> content is static and therefore does not have to be created
> dynamically. Probably we have a news section and a download section
> which should be generated dynamically (via continuous integration
> server) or feeded from our demo server.
>
> However a first prototype is available under
> https://incubator.apache.org/clerezza/spike/
>
> feedback is welcome (https://issues.apache.org/jira/browse/CLEREZZA-448)
>
> cheers
> tsuy
>
Re: website apache clerezza
Posted by Reto Bachmann-Gmuer <re...@trialox.org>.
Hi Tsuy
I see no reason not to eat our own dogfood and create the website using
Clerezza as we're currently doing.
Reto
On Wed, Mar 16, 2011 at 5:08 PM, Tsuyoshi Ito <ts...@trialox.org> wrote:
> Hi
>
> I am working on the html prototype of the clerezza website. I want to
> ask if somebody knows if there are any best practices on how to
> deploy/maintain an apache website (xsite?). IMO most of the website
> content is static and therefore does not have to be created
> dynamically. Probably we have a news section and a download section
> which should be generated dynamically (via continuous integration
> server) or feeded from our demo server.
>
> However a first prototype is available under
> https://incubator.apache.org/clerezza/spike/
>
> feedback is welcome (https://issues.apache.org/jira/browse/CLEREZZA-448)
>
> cheers
> tsuy
>