Make software objectives clearer

[PonteIneptique]

Hi everyone, and mostly people not using Capitains at the moment ! In an effort to make our codebase clearer, I tried the following diagram. It will have links to the different repositories or documentation to make things easier. I thought to maybe put it in the front page.

What do you think ?

PS : I removed Sparrow as it is not in a good shape right now.

[aurelberra]

Very nice, and helpful, indeed! It will just need to be polished ("Python" not "python", lowercase "Build", "Build", "Mine").

You could also use your nice little logos where applicable.

I'm wondering how you could make it clear that the paths are or can be complementary: longer paths tend to be felt as better ways?

[PonteIneptique]

So typos are corrected :

The issue is I did not want to bloat the graph, the idea is to get links to specific places. But maybe logos would be cool... I'll try and put this here once I find myself with a better internet connection.

The current interactive output is : http://capitains.org/capitains.workflow.html

[PonteIneptique]

I forgot one point : relation between software. I might actually make a second diagram for that, as I fear this would make things WAY too complicated...

[balmas]

this is great