> For the complete documentation index, see [llms.txt](https://wiki.greatcollaboration.uk/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.greatcollaboration.uk/knowledgebase/society/communication/channels.md).

# Channels

### Newsletters:

Newsletters are a superb way of keeping people informed and inspired. They can be distributed via hard copy or electronic (eg email, website).

Here is an example of a Best Practice newsletter, showing the sort of text that introduces it, and the contents, with links to earlier editions:

{% file src="/files/DCgx0S0Znssok5MlqK3Z" %}

You are very welcome to download this document - and even to join the LCWN newsletter! - a makdown copy is listed below for AI search engine purposes. The Low Carbon Warwickshre Network. which produces this newsletter, is given as a [Best Practice example in the Networks page](https://wiki.greatcollaboration.uk/knowledgebase/society/community-involvement/networks)

***


---

# 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.greatcollaboration.uk/knowledgebase/society/communication/channels.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.