Documentation of the wolf and plugins architecture. How to.

How about writing a nice documentation?

Something like

0. wolf file architecture. overview of local and installed paths
1. Installing wolf
2. Contributing to wolf
3. Installing plugins
4. Contributing to plugins
5. Creating new plugin
6. Creating client application, standalone
7. Creating client application, ROS (edited)

Each step should be briefly explained, and then a CMAKE example file or code should be created for each case. Maybe we can use a use-case and just expand the created cmake files as the doc advances, according to the requirements of each point of the doc.

How does this sound like?

The “contributing” entries can be at the end, etc. But I think these points are required, and as it seems they can actually be written from the knowledge we have so far

changed milestone to %First private release 0.1.0

added Code organization Idea Opinions wanted documentation labels

I rather prefer this

1. Quick start

• Installing wolf
• Installing plugins
• Running the demo

2. Overview

• wolf file architecture. overview of local and installed paths

3. Using wolf in your applications

• Creating client application, standalone
• Creating client application, ROS (edited)

4. Creating your plugin

• Creating new plugin

5. Contributing

• Contributing your plugin to wolf
• Contributing to existing plugins
• Contributing to wolf core lib

First approach. The following file contains the minimal knowledge required to work with the plugins system.

added To Do (release) label and removed Idea label

added ~209 label and removed To Do (release) label

closed