Consider shifting the focus of documentation from robustness to functionality

Most of the documentation I can see is focusing on “how well it can work” rather than “what it can do”, e.g. “parallelity”, “human interaction” . The latter are basically just introduced by SDK samples, which are not as understandable as well-explained documentation.

The robustness is no doubt one of the things that Temporal is better than its competitors. But also think about this: some people are interested in Temporal because they are sick of low-code and they want to see how Temporal can do the same thing a bpm-based workflow engine can do.

And during daily development, most will focus on how to implement some special logic, rather than good performance or HA. If they can just read the doc instead of digging into samples to “figure out” a solution, then their life can be easier.

@Jian_Chen thanks for the input. Temporal is open source, and community is more than welcome to give their inputs and help us improve. Here is the link to the docs repo where everyone can open issues and suggest/request improvements.

most will focus on how to implement some special logic,

Temporal docs include some getting started guides and its complimented by the samples repos. Both are growing and we are working hard to make them even better. The forum here is also a great reference and if you search around you will see that we provide help for specific impl questions, so if you have some, feel free to ask.

1 Like

Hi @Jian_Chen I am just following up here to see if you can provide some specific examples to help us align on exactly what you mean.

Are there any specific pages that you were looking at?
Was there something specific you were trying to do that you were not able to?

And any other additional context would be greatly appreciated.