> 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/basics-community-journalism/introduction.md).
# Introduction
## **What to expect in this chapter đź“–**
In this section, you’ll find practical guides on community journalism. Our aim is to equip you with the essential knowledge to successfully launch a community-centred media project. We focus on the fundamentals that will help you lay the groundwork for community-driven work right from the start.
What exactly is community journalism? What are the first steps in building a community? How do I create a community database? You’ll find answers to all these questions in the following section.
**🔍 Do you have a specific question and don’t want to search through the entire wiki? Use the search function or the AI assistant at the top right — you’ll quickly find what you need.**
***
## **A wiki you can shape 🙌**
This wiki thrives on participation: it’s created for and with you! Whether you have questions, want to give feedback, or contribute your own content like examples, practical tips, or templates — we welcome every contribution. Just use the froms below to get involved and help actively shape the wiki.
Ask a question or Make a contribution or Give feedback
---
# 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/basics-community-journalism/introduction.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.