Hi, Mauro. Understod - cool. I should say I'm very willing to help submit changes for review, rather than bang on about them in e-mails, once I've got my head round the process.
Jon -----Original Message----- From: Mauro Talevi <[email protected]> Reply-to: [email protected] To: [email protected] Subject: Re: [jbehave-user] Suggestions for jbehave.org Date: Thu, 07 Apr 2011 15:59:35 +0200 Hi Jon, thanks for feedback. We are in the process of revamping the website. The current structure is due to historical reasons, when it was mostly wiki based. Since then most docs have been moved to static html that is versioned and released for off-site consultation in the distribution archives. The idea is to maintain the multiple version reference docs and revamp the front-end to allow easier access to the stable docs. It's still to be decided if we'll keep WP for the front-end (there is the possibility to use static home pages) or just keep it for blog/news. For information, the http://jbehave.org/documentation/ has always been up-to-date in terms of links (the process is automated), it's the name of the links that were not. That is now fixed. We'll improve the how-to-contribute section. Cheers On 07/04/2011 07:14, Jonathan Woods wrote: > 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
