Once everything is in the wiki, we can move things around as we wish.
Uli
On 26.02.2010 18:01, Sebastian Hennebrueder wrote:
Sebastian Hennebrueder schrieb:
Ulrich Stärk schrieb:
It has and this is also the recommended approach since documentation
is considered part of the product. Only individuals who have signed a
CLA should be allowed to edit the docs.
Uli
On 26.02.2010 15:07, Thiago H. de Paula Figueiredo wrote:
On Fri, 26 Feb 2010 10:01:06 -0300, Ulrich Stärk <[email protected]>
wrote:
I guess we will have two versions of the documentation: latest (trunk)
and stable (5.1 for now).
+1 to that. Does the wiki has any access control}? If so, we can hava
the main documentation editable only by committers and have some are
where people can contribute pages.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Hello,
there was a discussion thread recently on this topic and though I
posted little, I have experimented with other solutions and discussed
possible options offline with Howard.
I planned to bring my ideas to the mailing list the next days. I have
experimented with Jekyll for my new webpages it is a static site
generator which is blog aware. It supports rendering of normal pages +
blog like pages. The latter could be used for news for example.
I wanted to do an experiment with Tapx to see if it could be an
alternative.
The nice thing is that it provides very nice markup alternatives:
textile and markup. Both are somehow Wiki like and very efficient to
use. Files can include plain HTML as well and syntax highlighting is
supported with Pygments for all kind of source code.
Links:
Sample of my new website to come with source code highlighting
http://test.laliluna.de/articles/jsf-2-evaluation-test.html
Jekyll
http://github.com/mojombo/jekyll
I hope to be able to continue working on this next week. As far as I
remember we got stuck, when deciding about the new layout.
Considering the version of documentation, I propose the following approach:
tapestry.apache.org has always the documentation for the latest
released. But opposed to the release, we allow updates. The simple
reason for this approach is that this version is the one that most
people will need and especially new users are interested in and still we
can continuously improve the documentation.
Once we have a new release, we tag the documentation and provide it on
an archive site.
Sample:
Current release of Tapestry: 5.1
Documentation of 5.1 is on tapestry.apache.org and is updated
continously. Changes have to be merged into the 5.2 branch as well.
New release of Tapestry 5.2
Documentation is tagged '5.1-latest' and the 5.2 branch is now put on
the tapestry.apache.org website.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
