> For the complete documentation index, see [llms.txt](https://docs.activist.org/activist/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.activist.org/activist/product/about/roadmap.md).

# Roadmap

Visit the [source code on GitHub ](https://github.com/activist-org/activist)to get involved!

activist.org is open-source software. Our goal is to build in as transparent a manner as possible so that partner organizations and our community can have as much input on the process as possible.

Please visit our [GitHub project space ](https://github.com/orgs/activist-org/projects/1)for a full overview of the current issues and features being worked on. For those ready to start contributing, check the following issue filters to find something to work on:

* [Good first issues for new contributors](https://github.com/activist-org/activist/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
* [Feature requests to add new functionality](https://github.com/activist-org/activist/issues?q=is%3Aopen+is%3Aissue+label%3Afeature)
* [Bug fixes to help us make a stable experience](https://github.com/activist-org/activist/issues?q=is%3Aopen+is%3Aissue+label%3Abug)

***

{% stepper %}
{% step %}

#### Product Research for MVP

Focus on understanding the unique needs of activists and organizations by conducting surveys, interviews, and community discussions. This will help identify key pain points and essential features that align with the platform's mission to support activism.
{% endstep %}

{% step %}

#### MVP Development and Launch (current stage)

Develop a minimum viable product with core features like organization profiles, event pages and join-flows. Prioritize rapid prototyping and gather initial community feedback to ensure the platform meets activists' needs and expectations.
{% endstep %}

{% step %}

#### Growth and new features

Scale the platform’s impact by implementing new features based on user feedback, such as event coordination tools and enhanced privacy options. Strengthen the community through outreach and partnerships, helping activist.org expand its reach and support network.
{% endstep %}
{% endstepper %}

***

{% hint style="info" %}
If you want to see these features realized rather sooner than later, consider [supporting us](https://docs.activist.org/activist/welcome/support-us) with your skills, reach or money.
{% endhint %}


---

# 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.activist.org/activist/product/about/roadmap.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.