Quoting Jeremy Daggett <[email protected]>:

I am in the process of adding a few new pages to the wiki, and would appreciate some feedback before pulling the trigger. Here is the new layout I propose for the front page of our wiki:

* Architecture <- new top level bullet
   * [[Core Concepts]] <- move “Core Concepts" to Architecture section

* Code
  * [[Coding Standards]] <- new page
  * [[Best Practices]] <- new page
  * [[Annotations]]

* Tools <- move “Development Environment” to a top level bullet called “Tools”
    * [[Eclipse]] <-- new page
    * [[IDEA]]

* Road Map <- move up to top level bullet

NOTE: the following top level bullets WILL NOT change:
* Contribute
* Release It!
* Community

Feedback appreciated, thanks!

I think the proposed structure makes sense, I'm just wondering about the "section headings" 'Code' and 'Tools'. How about e.g. 'Coding', 'Development Guidelines' or 'Writing jclouds Code' for the former and the original 'Development Environment' or 'Your Development Environment' for the latter? Perhaps also 'Understanding jclouds' for 'Architecture'?

I know they're a bit longer, but I think they may make it easier for the new reader to find what they're looking for?

Thanks for taking this on, Jeremy!

ap

PS: A link from 'Tools' to the 'Logging' page on the main site would make sense, I think. As would a new page 'Running live tests'! We've had a couple of forum questions about this recently, and have "lost" the original page [1] as part of the site redesign.

[1] http://2bfcdbe0cc28b674f568-6e84ef02f7d038e5f4526bc5b8a12a51.r1.cf1.rackcdn.com/documentation/devguides/provider-testing/

Reply via email to