> 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/the-bristol-cable-england/how-the-bristol-cable-started.md). # How The Bristol Cable started The Bristol Cable was founded in 2014 by Alec Saelens, Adam Cantwell-Corn, Alon Aviram, leading a group of volunteers. On launching, they raised £3,300 in a crowdfunding campaign, £1,500 from Co-ops UK, and £1,600 from Lush. In the six months prior to the first print edition the Cable organised a [series of journalistic workshops in different parts of the city](https://www.journalism.co.uk/news/how-the-bristol-cable-wants-to-democratise-local-media-/s2/a556313/). The workshops were free of charge and could be attended by everyone. They focussed on topics such as investigative journalism, filming with smartphones and police reporting. The workshops were designed to find volunteers, publicise the idea of the Cable and ensure that the participatory nature of making many different voices heard was guaranteed. The Bristol Cable was also organised as a cooperative from the outset, in order to make a new case for the financing of local journalism. After a year and a half there were about 500 members paying £2.50 on average. The first major grant that secured the Cable's core funding over two years was $120,000 in 2015 from the Reva & David Logan Foundation based in Chicago, USA. It was followed by another $180,000 core funding plus $75,000 match funding over three years in 2017. In 2018, Luminate (formerly Omidyar Network) decided to fund Cable with $275,000 until 2020. The funding was extended for three years in 2020 (in the amount of $450,000) and secured a large part of the Bristol Cable's budget until 2023. --- # 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/the-bristol-cable-england/how-the-bristol-cable-started.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.