# imdone.io Site Map

**Last Updated:** February 9, 2026

## Overview
imdone helps developers solve the shared context problem by keeping issues, decisions, and context in markdown files next to code in the repository.

---

## Main Pages

### [Homepage](https://imdone.io/)
The shared context problem and how imdone solves it. Choose between CLI and Desktop workflows.

**Keywords:** shared context problem, context-driven development, markdown issues

---

## Product Pages

### [imdone CLI](https://imdone.io/imdone-cli)
Command-line workflow for developers who live in the terminal.

**Features:**
- Sync Jira and GitHub Issues to markdown files
- Edit in vim, VS Code, or any editor
- Grep your backlog like code
- Work offline, sync when ready

**Keywords:** CLI task management, terminal workflow, grep issues

### [Markdown Kanban Board](https://imdone.io/markdown-kanban-board)
Visual desktop app with drag-and-drop kanban interface.

**Features:**
- Drag-and-drop markdown TODOs
- Visual board in your editor
- Works with existing markdown
- Desktop app for Mac/Windows/Linux

**Keywords:** markdown kanban, visual task board, desktop app

---

## Team & Enterprise

### [For Teams](https://imdone.io/for-teams)
Collaborative features for engineering teams.

**Features:**
- Ensemble programming support
- Shared context across team
- Team workflows
- Collaborative issue editing

**Keywords:** team collaboration, ensemble programming, shared context teams

### [Markdown Jira Sync](https://imdone.io/markdown-jira-sync)
Bidirectional synchronization between Jira and local markdown files.

**Features:**
- Pull Jira issues to markdown
- Edit locally in any editor
- Sync changes back to Jira
- Keep issues in git history

**Keywords:** Jira markdown sync, bidirectional sync, local Jira editing

### [Markdown GitHub Issues Sync](https://imdone.io/markdown-github-issues-sync)
Bidirectional synchronization between GitHub Issues and local markdown files.

**Features:**
- Pull GitHub Issues to markdown
- Edit locally in any editor
- Sync changes back to GitHub
- Keep issues in git history

**Keywords:** GitHub Issues markdown sync, bidirectional sync, local GitHub editing

---

## Pricing & Plans

### [Plans](https://imdone.io/plans)
Flexible pricing for individuals and teams.

**Plans Available:**
- Free tier
- Individual plans
- Team plans
- Enterprise plans

---

## Resources

### [Documentation](https://imdone.io/docs)
Complete guides for imdone CLI and Desktop.

**Topics:**
- Installation
- Configuration
- Workflow tutorials
- API reference
- Best practices

### [Community](https://imdone.io/community)
Join the imdone community.

**Connect:**
- Discord server
- GitHub discussions
- Community support
- Feature requests

---

## Legal

### [Privacy Policy](https://imdone.io/privacy)
Privacy policy and data handling practices.

### [EULA](https://imdone.io/eula)
End user license agreement and terms of use.

---

## Site Structure

```
imdone.io/
├── Homepage (/)
├── Product Pages
│   ├── CLI Workflow (/imdone-cli)
│   └── Desktop Workflow (/markdown-kanban-board)
├── Features
│   ├── For Teams (/for-teams)
│   ├── Markdown Jira Sync (/markdown-jira-sync)
│   └── Markdown GitHub Issues Sync (/markdown-github-issues-sync)
├── Pricing (/plans)
├── Resources
│   ├── Documentation (/docs)
│   └── Community (/community)
└── Legal
    ├── Privacy (/privacy)
    └── EULA (/eula)
```

---

## Core Concepts

**Shared Context Problem:** When issues, decisions, and context drift away from code, teams lose alignment and adaptability.

**Solution:** Keep everything as markdown files in your repository, next to your code.

**Two Workflows:**
1. **CLI:** For terminal-focused developers
2. **Desktop:** For visual kanban thinkers

**Key Benefits:**
- Work offline, sync when ready
- Grep your backlog like code
- Git history for all changes
- Bidirectional sync with Jira/GitHub
- Shared context enables team adaptability