Brief description

I think it would be nice to have a design review template companies can use internally when deciding how to build something with Temporal. Inspired by this SO question: https://stackoverflow.com/questions/72493152/what-should-i-consider-when-using-cadence-temporal-to-design-a-new-project

This seems more like an opinionated piece and so should be left to a Dev Rel or Dev Advocate? It seems like a necessary part, but technical documentation should try to document what is rather than what should be.

I don't have a pref on who writes it. Is that the only reason you draw the distinction? Re: the issue title, [Documentation request] is the only option besides "functionality bug report". Re: where the content will live, I prefer somewhere in docs.temporal.io but outside of the blog. Same for related future "what should be" content, like our design patterns guides and "Distributed Systems Pattern X in Temporal" content.

Agree this is a priority for Dev Rel — closing this issue since it's not getting any more attention here, but happy to continue this conversation!