Update architecture section

[nilshempelmann]

• include new WPS e.g. pelican
• Extend functionallity description
• update/ add graphics

[nilshempelmann]

Architecture might be missleading. birdhouse doc contains the 'framework or organisation or ecosystem' with all the modules. pavics is a real project realissation with an technical existing architecture physically on serveral servers. The problem is not new : #17

…

On 01/10/2019 16:37, David Huard wrote: A general question is how do we bring together birdhouse-docs and pavics-sdi ? pavics-sdi should be a superset of birdhouse-docs, adding elements of information specific to a given deployment. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#40?email_source=notifications&email_token=ACB5JKWHZEAYQO7HTT5X4FLQMNOD5A5CNFSM4I4J77J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEABP5JI#issuecomment-537067173>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACB5JKVYRKC25Y256SUONYLQMNOD5ANCNFSM4I4J77JQ>.

[Zeitsperre]

It certainly isn't. I know we haven't moved too much within the Bird-house documentation but we have identified a few sphinx extension technologies that can help in linking the documentations of various birds. We have it employed on a few PAVICS services. I'll link the software here once I find it.

[nilshempelmann]

related to #38

[huard]

@Zeitsperre Are you referring to ReadTheDocs subprojects ?

[Zeitsperre]

@huard yes, thanks!

[nilshempelmann]

former architecture is now the birdhouse-framwork and updated.

former project section are going to be architecture-examples

To be further improved!