> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/burgerportal-bergisch-gladbach-germany/biggest-success-factors.md). # Biggest Success Factors By prioritizing the newsletter as its primary journalistic product, Bürgerportal has successfully cultivated a considerable organic reach and established itself as a dependable digital daily newspaper, reliably delivered to readers' inboxes at 7 a.m. This autonomy over reach, independent of external factors, constitutes one of the two critical success factors for the platform. The other pivotal factor is the "Freundeskreis" community, which not only contributes significantly to the revenue mix but also serves as the heart of Bürgerportal. The entire community journalism approach revolves around this community. Through deep and regular engagement with its members, Bürgerportal has become deeply integrated into the city's social fabric, a feat unmatched by competitors like the Kölner Stadtanzeiger. Moreover, it is through this community that Bürgerportal fulfills its mission of being a comprehensive local journalism provider for Bergisch Gladbach, as community members contribute stories on topics that would otherwise be overlooked due to the constraints of the small team. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/burgerportal-bergisch-gladbach-germany/biggest-success-factors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.