I understand your concerns related to the documentation we ship. In this
case I'm thinking how a README file should look like? First thing that pops
into my mind is that all READMEs should have a consistent feel and probably
include the same topics like:
  - running the sample
  - short presentation of the technologies involved
  - short presentation of the composite
  - more advanced SCA terminology and concepts explained (which are used in
the sample)

Please add other topics which you feel they need to be part of it.

As an alternative, I was thinking about a problem/solution format but I
don't think we can apply that to all our samples...

Reply via email to