Hello,
I finished the last open tasks for the new website. I would appreciate,
if we get this finished as soon as possible as I need to focus on my
normal work for the next weeks. In addition, we have to continuously
update the current status in case changes happen to existing docs, so it
would be nice to get this in the trunk as soon as possible.
So please core committers, if possible take some time to get this
finally decided. Most of the work is done anyway, it is more a question
of getting the content into the subversion repository and staging the
content.
The website can be tested here http://tapestry.laliluna.de and you can
get the current status from my git repository:
git clone http://dev.laliluna.de/public/tapestry-website.git/
tapestry-website
I fixed the broken links reported by Ivano and repaired the JQuery
documentation in order that the correct menus are always open.
I integrated the userguide in the website in order to show how it would
look like.
I discussed with Howard that there are mainly two options to place the
userguide. Howard points out that the current approach to have the user
guide integrated in the tapestry project, makes it easier to keep it
aligned with the source code version and doesn't require a second commit
to be done. It might be more likely that the doc gets updated in that case.
My proposal is to integrate the userguide into the normal webpage
because of two reason. We can continously work on the userguide and
publish updates from time to time without waiting for the next release
to come out. My strategy for the branches look like this.
The website is published from a 'toPublish' branch. This branch has
currently the 5.1.0.5 documentation. We allow this branch to be updated
as long as the 5.1.0.6 release appears. Then a 5.1.0.5 tag is made. The
most current work happens as usual in the trunk, but as I said before,
be might update the current published branch from the changes in the
trunk. We have a slightly higher effort when adding content to the
current published version but at least can do it and we have still a
kind of alignment to the code.
Both options are possible and it would be nice if this is decided as
soon as possible. We can change this back at any time. It is more or
less a copying of about 10 files from A to b and a minimal change in two
site.xml
Please state your opinion, if the website proposal is fine or not.
Andreas pointed out that we might move the new website to GitHub. You
need to decide as well, if we do this or keep everything in the normal
subversion repository. My private repo is only a temporarily solution.
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-----
Software Developer and Trainer for Hibernate / Java Persistence
http://www.laliluna.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
