# Contributing to Open Notebook

**📍 This file has moved!**

All contribution guidelines have been consolidated into the new development documentation structure.

👉 **[Read the Contributing Guide](docs/7-DEVELOPMENT/contributing.md)**

---

## Quick Links

- **Want to contribute code?** → [Contributing Guide](docs/7-DEVELOPMENT/contributing.md)
- **Want to understand the architecture?** → [Architecture Overview](docs/7-DEVELOPMENT/architecture.md)
- **Want to understand what we're building?** → [Vision & Principles](VISION.md)
- **Want to understand our engineering practices?** → [Design Principles](docs/7-DEVELOPMENT/design-principles.md)
- **Are you a maintainer?** → [Maintainer Guide](docs/7-DEVELOPMENT/maintainer-guide.md)
- **New developer?** → [Quick Start](docs/7-DEVELOPMENT/quick-start.md)

---

## The Issue-First Workflow

**TL;DR**: For anything non-trivial — features, architecture changes — create an issue first, get
it assigned, THEN code. Small obvious fixes (typos, docs, tiny bugs) can go straight to a PR.
Already coded something bigger? Mark the PR as draft and open the issue — triage takes 1–2 days.

This prevents wasted effort and ensures your work aligns with the project. [See details →](docs/7-DEVELOPMENT/contributing.md)

---

For all contribution details, see **[docs/7-DEVELOPMENT/contributing.md](docs/7-DEVELOPMENT/contributing.md)**.