System Architecture
The core has a desktop shell that hosts dock-able windows, contains a Scripture Editor, and provides discovery and management of available extensions.
There are four processes that make up Platform.Bible. The main process acts as the central message router for all other services. It hosts the web server that all other services connect to through sockets when joining the network. It is where data handling and electron begins. The renderer process starts the extension host and renders the web views. The extension host is the node process that loads in the extension container for all extensions. The c# data provider is a thin wrapper around Paratext data that gives access to usfm.
The Platform.Bible API (PAPI) is the main avenue of communication between processes in the Platform.Bible architecture. The PAPI is built primarily for this communication but it can also be used by extensions. PAPI gives discoverability of extension APIs.