A definitive guide + architectural diagram for Temporal will be key when we all finally start using it in production, both for developers and business POV - many adopters will have to make a business case covering running cost, operational consideration and complexities, security baseline etc.
Some points to cover;
- Components Diagram (both internal and external eg db, Kafka etc)
- Network flow
- Data flow
- Minimum system requirements
- Recommended system requirements
- Recommended deployment models >> docker, k8s (orchestration) | aws, gcp, azure (cloud)
I can see this being split into Developer Guide, Operations Guide.