> ## Documentation Index
> Fetch the complete documentation index at: https://docsgetmyordo.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Ordo

> Why Ordo is built around focused planning and real execution

Ordo is project management that stays out of your way.
This docs site is built to get you up and running fast, then help you operate it confidently.

## Where to Begin

* [Quick Start](https://docsgetmyordo.mintlify.site/core/index.md) for the fastest path to your workspace
* [GitHub Integration Setup](https://docsgetmyordo.mintlify.site/core/integrations/github/setup.md) for repo sync
* [Gitea Integration Setup](https://docsgetmyordo.mintlify.site/core/integrations/gitea/setup.md) for self-hosted Gitea
* [Outgoing webhooks](https://docsgetmyordo.mintlify.site/core/integrations/outgoing-webhooks.md) for Slack, Discord, and custom HTTP notifications
* [API Introduction](https://docsgetmyordo.mintlify.site/api-reference/introduction) for authenticated API usage

## Why Ordo Exists

Ordo follows a simple idea: **all you need, nothing you don't**.

Ordo was built because we were tired of project management tools that got in the way more than they helped. After years of using bloated, overcomplicated platforms that distracted from actual work, we knew there had to be a better way.

The problem wasn't that these tools lacked features—it was that they had too many. Every notification, every unnecessary button, every complex workflow was pulling teams away from what mattered: building great products.

We believe the best tools are invisible. They should amplify your team's natural workflow, not force you to adapt to theirs. Ordo is built on the principle that less is more—every feature exists because it solves a real problem, not because it looks impressive in a demo.

## Planning in Ordo

Planning in Ordo is intentionally lightweight: you define the work, assign clear ownership, and move forward without ceremony.

Labels are central to that flow. Use labels to group initiatives, surface cross-cutting work, and keep prioritization clear across board and list views.

* Use labels to represent streams like `onboarding`, `backend`, or `customer-feedback`
* Combine labels with priority and due dates for sharper planning
* Keep label naming consistent across the workspace so filtering stays useful

## Continue

* [Authentication Providers](https://docsgetmyordo.mintlify.site/core/social-providers/github.md)
* [Migration Guide](https://docsgetmyordo.mintlify.site/core/guide/migrating-from-v1)
* [API Reference](https://docsgetmyordo.mintlify.site/api-reference/introduction)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.