> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/wiki/pr-and-outreach/blog.md). # Blog The blog is something like a big playground. Of course, for CorrelAid, it also has a purely practical function: we publish reports about our meetings, events, etc., and then share them on social media – classic public relations work. So if you want to share something from your local chapter (like a report about a hackathon or the like), just join the slack channel #pr-blog! At the same time, the blog also offers CorrelAid members the opportunity to share their ideas or analyses. This can start very small with a small evaluation/visualization or an explanation of a statistical phenomenon. But it can also lead to a large, comprehensive analysis with various interactive graphics. If you have ideas, just write to slack #pr-blog. Finally, if it turns out, we are always happy to have guest posts or cross posts on our blog. So if you know someone outside of CorrelAid (scientists, activists etc.) who we should collaborate with, please shout it out in Slack. --- # 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://docs.correlaid.org/wiki/pr-and-outreach/blog.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.