As Sylvain got documentation ideas rolling, here's some suggestions
for OCL:

As Peter already comments at the bottom of the current OCL page (in
2006) I think we should really improve the OCL presentation. OCL will
be the *main* reason people use OROCOS: because they browse through
OCL and find all those sweet components which will save so many hours
of work. I would also (in the long run) suggest to allow external
component contributers to maintain their components and documentation
within OCL.

Ideas:

On the OCL front page "Components for Control" make the description a
one-liner (maybe a table) and link to individual wiki pages which each
describe one component with a default template containing:

- short description
- version
- dependencies
- maintainer
- real-time?
- license
- detailed usage intsructions
...

For example take a look at the "Egg" repository of Chicken Scheme
(Eggs are extensions which extend the base chicken scheme language)
Each egg has its own little page:

http://chicken.wiki.br/Eggs Unlimited 3

Probably stubs for such wiki pages could be fairly easily generated
from the components themselves.

Assign each component a maintainer, even if it's mostly the same
persons initally. This will change.

Get rid of "Components Overview" (which links to "The Orocos Component
Library") by moving the documentation of these components as described
above into the wiki.

One orocos.org rename "Components Tutorial" (which links to "Tutorial
on the Component Interface") to "Component User Manual" which makes
the distinction to the "Component Builders Manual" much clearer.

What do you think?

Best regards
Markus