Architecture of this Admin project

[robertellisuk]

1. If I have an existing IS 6 database, do I just point all of the connection strings in this project, to that database? Or am I supposed to have two database, 1 for IS 6, and 1 for this Admin project? If the latter, then which connection strings should be pointing to which databases?
2. Why does...
   Skoruba.Duende.IdentityServer.STS.Identity
   ... exist in this project? Does this project include not only an Admin GUI for IS6 databases, but also an STS implementation for IS 6? Why is STS part of this project at all?
3. Is there any documentation for the section which involve configuring certificates for signing purposes?
4. Are there any architecture diagrams which illustrate how IS 6, Admin, databases, certificates, and runtime (for example, IIS/Azure App Service) all fit together and showing the relationships between all of these components?
5. Is there any way (including entirely outside the scope of this project) to deploy a low-cost. modern Identity Server implementation, into a cloud environment, with an Admin UI, which is accessible and straightforward for the novice to get up and running and to use?