“WHY COMMUNITY IS MORE REPRESENTATIVE THAN “USERS”
In the traditional software development model, we're used to writing technical documentation with a specific user in mind. However, this approach can be limiting because it assumes a single "ideal" user represents your entire user base.

The docs-as-ecosystem model proposes a different way of thinking about technical documentation; it recognizes technical documentation is not just a product but an ongoing conversation between diverse documentation creators (contributors) and the community.

Thinking in terms of community has several advantages over focusing only on users:

More inclusive: Focusing on the community is more inclusive than focusing only on users because it recognizes that many different types of stakeholders contribute to and read the documentation.

More diverse: Focusing on the community encourages diversity and inclusion because it recognizes many different backgrounds and experiences.

More collaborative: Focusing on the community also fosters a more collaborative approach to documentation because it encourages anyone from any background to participate.

By focusing on community, the docs-as-ecosystem approach offers a more flexible, adaptable, and sustainable way to approach technical documentation. Rather than assuming that there is a single "ideal" user, we recognize that technical documentation is a dynamic and ongoing conversation between documentation creators and the community.”