> 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/mecseki-muzli-hungary/community-journalism.md).

# Community Journalism

Mecseki Müzli distinguishes between its broader audience and its core community, with the latter actively participating in the newsroom's operations, particularly through two engagement initiatives:

1. The audience content loop: Subscribers are encouraged to submit topic ideas for feature or long-form articles. The team reviews these suggestions and selects those deemed feasible. Then, a vote is held among paid subscribers to choose from three selected topics. Once an article is published, subscribers are asked for feedback on the piece.
2. Open editorial meetings: Subscribers are invited to join editorial meetings, and despite the potential for low attendance, the first meeting saw 10 participants. For Güth, this represents an opportunity to foster greater loyalty and increase the relevance of the content produced.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/mecseki-muzli-hungary/community-journalism.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.