incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmuer <>
Subject Re: How to modify pages on the project website
Date Thu, 07 Apr 2011 05:07:53 GMT
Hi Marco,

Even when you're not a developer you're free to proposes patches to the
website publication process as well as to the website content itself. It is
requirement on a process however that all content is stored in svn, so
simple SFTP isn't an option.

Also keep in mind that documentation should mainly be available in the
documentation both published on the website as well as being available
online on a clerezza instance. So the process should take this into account.

As mentioned in an earlier mauil to the subject, you're also welcome to
raise issues against the current content, this issues may be accompanied by
a patch but may also just describe the typo in the text. Even for the
technical audience the content needs to be revisited, the start page
advertises a non existent front end adaptor for the sesame api.


On Thu, Apr 7, 2011 at 5:53 AM, Marco Zaugg <> wrote:

> Hi there
> I'd like to contribute my non-techie time to work on
> the project website
> as the current site contains many typos, missing content
> for IT executives, Non-SemWeb savvies etc.
> Although not usual in the developer world I thought even
> contributing summaries of what Apache Clerezza is about
> in different languages.
> Question: How do I modify the content without being a
> Clerezza Core developer. I'm looking for whether a
> simple SSH/SFTP access to HTML files or a simple CMS
> that I can use to populate the content. Of course somebody
> of the core team will have to approve the content.
> In order to improve the speed of developer howtos and
> further documentation I would rather use a wiki such
> as Confluence or similar. My company is partner of Atlassian
> and therefore able to provide a customized Apache Clerezza
> Wiki skin.
> I challenge the current process of updating content as it
> seems to be too time consuming and over-engineered for what
> the community need. If you want good quality documentation you
> have to lower the hurdles for those that are willing to
> contribute. If you'd like to showcase the capabilities of
> Apache Clerezza don't do that jeopardizing the easyness of
> updating content. This actually is one of the leasons learned
> in the knowledge management world that came out with wikis
> as one of the answers to that.
> Marco

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message