> 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/pionier-portrats/the-bristol-cable-england/grosste-herausforderungen.md).

# Größte Herausforderungen

Die größte Herausforderung ist das Sammeln von Geld. Vor allem, weil die Hauptfinanzierung von Luminate 2023 ausläuft, hat das Sammeln von Geld viel Energie im Team gekostet. Seit Ende 2023 läuft eine Mitgliederkampagne, um den Verlust der Finanzierung auszugleichen. Das langfristige Ziel ist, dass Bristol Cable sich komplett aus den Beiträgen der Mitglieder finanzieren kann.


---

# 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/pionier-portrats/the-bristol-cable-england/grosste-herausforderungen.md?ask=<question>&goal=<user_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.