Hi,
Few people contacted me personally to ask how they can contribute to the
reference guide.
I've just added
http://martin-g.github.com/wicket-reference-guide/howtohelp.html that
explains the steps.
Let me know if I can improve it. Or just me a patch ;-)
--
Martin Grigorov
jWeekend
Training, C
> Few people contacted me personally to ask how they can contribute to the
> reference guide.
> I've just added
> http://martin-g.github.com/wicket-reference-guide/howtohelp.html that
> explains the steps.
>
> Let me know if I can improve it. Or just me a patch ;-)
is there the intention to deprec
On Wed, Feb 6, 2013 at 11:33 AM, manuelbarzi wrote:
> > Few people contacted me personally to ask how they can contribute to the
> > reference guide.
> > I've just added
> > http://martin-g.github.com/wicket-reference-guide/howtohelp.html that
> > explains the steps.
> >
> > Let me know if I can
why doesnt the guide live in a subdir of the project. that way there
will be a guide per branch. one of the biggest problems with the wiki,
etc, is that it doesnt account for code differences between the
versions. having a guide per branch (major version) makes more sense.
-igor
On Wed, Feb 6, 20
This is how it is, actually.
In Wicket Git repo there is a branch 'reference-guide' that has a Maven
module 'wicket-reference-guide'.
The branch will be merged to master once we feel confident that
documentation generation works and we like the way it works.
So Wicket 6 will have its own version o
