Synchronizing Birdhouse and PAVICS Documentations

[Zeitsperre]

As was discussed, we should be trying to flesh out the documentation of Birdhouse with common elements in pavics-sdi. I'm currently reading through both documentations and familiarizing myself with sphinx libraries. Issue discussion at pavics-sdi can be found here: https://github.com/Ouranosinc/pavics-sdi/issues/15

[nilshempelmann]

To respect and promote the Projects here is a section for it now: https://birdhouse.readthedocs.io/en/latest/projects.html

Former section "projects" is renamed to 'components'

[nilshempelmann]

@huard @cehbrecht The FP processes documentation is updated and can be used as reference in Pavics.

I suggest to move (and adopt) the Pavics tutorial to the Birdhouse Documentation.

[nilshempelmann]

@huard as suggested by @cehbrecht there is now a notebook repository https://github.com/bird-house/notebooks. Right place for tutorials

[nilshempelmann]

@huard As discussed at last VC here a 'roadmap' or suggestion of what should be documented where:

• Birdhouse Top-level documentaion : General aspects like principals, publications, guidlines, coding style and general tutorials
• birds and modules: module specific information, process methodes, additions to the linked general documentation (the cookycutter should provide the appropriate links to the top-level documentation)
• project docs: Project specific Information. User related tutorial and explanaiton. I see Project docs User orientated, while Birdhouse docs are developer orientated

[Zeitsperre]

@huard with #44 Are we good to close this issue?

[huard]

I think the last step would be to configure subprojects inside birdhouse to include documentation from individual birds in the search index.