Having just gone through the initial (steep and sometimes pitfall-scattered) learning curve, I could definitely help sketch out some ideas and possible contribute to the documentation. Do I need to get a confluence account set up? (I'm not sure how much time I can commit, but I'd like to contribute what I can to help others with their initial forray into SM.)
Terry wrote: > >> Any ideas on how to do that ? > > You need more than one way to get to information as people will use > different strategies to find out about a new technology. I personally > like to know at a glance the scope of a project, so I preferred the > original approach (and the one taken on the ActiveMQ site) of having > lots of left menu items for each topic, component or significant point. > > The documentation is probably weakest on practical examples, judging by > the sort of support queries coming in. There should be explicit > tutorials for binding to a foreign web service, exposing a web service, > wrapping a POJO, creating JBI components, packaging and deploying using > su/sa, applying security. > > We also need to do a better job of keeping these up to date and making > it clear which documentation refers to which release. > > > -- > Terry > > -- View this message in context: http://www.nabble.com/Doc-reorg-tf3269938s12049.html#a9099189 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
