> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-hacktivists/logos-hacktivist-training.md).

# Logos Hacktivist Training

The [Logos Hacktivist (Activist Builder) training](https://learning.logos.co/course/view.php?id=4) is a self-paced course that explores how your skills and ideas can contribute to the Logos ecosystem. From supporting Circles with practical technical needs to experimenting with the Logos stack and building long-term infrastructure, you'll discover different ways to get involved.

#### What you'll learn

* **The Logos vision:** How Circles contribute to building a parallel society.
* **User-driven development:** How to identify real problems, validate needs and build solutions that people actually use.
* **The Logos technology stack:** An introduction to Logos Blockchain, Messaging, Storage and Basecamp, including nodes and developer resources.
* **Building on the ecosystem:** How to collaborate with Circles and EcoDev, contribute to open-source projects and develop reusable infrastructure.

The course gives you the foundations to support communities, explore technical opportunities and contribute to the wider Logos movement.

#### Get started

You can [start the Hacktivist training](https://learning.logos.co/course/view.php?id=4) immediately and work through it at your own pace.

Prefer to talk to us first? [Get in touch with the Logos team](https://logos.co/activist-builder) to discuss how you could get involved.


---

# 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://circles.logos.co/readme/for-hacktivists/logos-hacktivist-training.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.
