I imagine the team have plans for structuring jbehave.org, but I felt
there were a few things which might improve the visitor's experience in
the short term and drive up engagement from potential contributors. (I
see from my language that I've been working with too many user
experience people.)
When I first hit jbehave.org, I thought the project wasn't being
maintained because I came across some legacy information without any
wider context, and that might be happening for others. I think that's
principally because jbehave.org/ and
jbehave.org/reference/stable|preview are largely separate and not very
mutually reachable. It would also be good to have some more detailed
info on how to contribute and keep the team happy.
Suggestions:
- link prominently and everywhere from /reference to /. The reference
site has pretty high search engine ranking, so this would help drive
people back to the root.
- at the out-of-date /documentation page, or instead of it, DRY and
instead point to a new page jbehave.org/reference, which itself points
to /reference/stable and /reference/preview. This would help people not
intimately familiar with codehaus site structures to see that there are
separate stable and preview documentation sub-sites.
- de-duplicate /development and the 'project info' section at
jbehave.org/reference, so there's one place for project info including
contribution how-to (next point)
- add a bit more information at /development/how-to-contribute,
including (i) whether suggestions should always be made in the first
instance by mails to user@ or dev@ (and which one) or whether JIRA is
ever acceptable straightaway; (ii) whether bugs or suggestions should
always be discussed first on one of the lists or direct JIRA additions
are acceptable (or even possible; haven't tried); (iii) whether git pull
requests are OK as a means of submitting change suggestions.
Jon
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
