# How we structured docs for user personas

DevFeed: [How we structured docs for user personas](<https://devfeed.tech/articles/how-we-structured-docs-for-user-personas-35777.md>)

Original publisher: [Read original article](<https://temporal.io/blog/docs-info-arch-2021>)

Author: Cully Wakelin

Published: 2021-05-06T07:00:00Z

Content type: opinion

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Users](<https://devfeed.tech/topics/users.md>)

Tags: [concepts](<https://devfeed.tech/tags/concepts.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [temporal-voices](<https://devfeed.tech/tags/temporal-voices.md>), [users](<https://devfeed.tech/tags/users.md>)

## AI overview

The article explains how Temporal restructured its core-concepts documentation around different user personas. It describes problems with the previous terminology-heavy approach and argues that users need both an explanation of Workflows and language-specific implementation details.

## Source excerpt

Refreshing the core concepts documentation area had become a major priority in my mind; that subset of docs had largely gone untouched in the last couple of years.