# Community Support for Open Notebook: Discord, GitHub, and Documentation Channels
> Get help with Open Notebook! Join our Discord, use GitHub for issues and discussions, or explore our documentation to find answers and contribute to the project.
- Repository: [Luis Novo/open-notebook](https://github.com/lfnovo/open-notebook)
- Tags: getting-started
- Published: 2026-07-03
---
**Open Notebook provides community support through a Discord server for real-time chat, GitHub Issues for bug reports, GitHub Discussions for design conversations, and comprehensive documentation.**
The open-source project `lfnovo/open-notebook` maintains a multi-channel support ecosystem designed to help users troubleshoot problems, share workflows, and contribute to development. Whether you need immediate assistance with an installation error or want to discuss architectural changes, understanding the available **community support for Open Notebook** ensures you reach the right audience through the appropriate channel.
## Real-Time Assistance via Discord
The fastest way to get help is the **Discord server** at `https://discord.gg/37XJPXfz2w`. This live chat platform appears in the "Community Support" section of [`README.md`](https://github.com/lfnovo/open-notebook/blob/main/README.md) and serves as the primary hub for troubleshooting, feature announcements, and user-driven discussions. The documentation in [`docs/index.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/index.md) repeatedly references Discord, and the [`docs/6-TROUBLESHOOTING/quick-fixes.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/6-TROUBLESHOOTING/quick-fixes.md) guide specifically recommends it as the fastest way to get assistance when documentation solutions prove insufficient.
## Structured Collaboration on GitHub
For reproducible issues and long-form development discussions, Open Notebook leverages the GitHub ecosystem across three distinct channels.
### Reporting Bugs and Requesting Features
**GitHub Issues** at `https://github.com/lfnovo/open-notebook/issues` serve as the dedicated tracker for bug reports and feature requests. The [`README.md`](https://github.com/lfnovo/open-notebook/blob/main/README.md) directs users here when they encounter reproducible errors or have specific enhancement ideas that require structured tracking, assignment, and milestone planning.
### Architecture and Design Discussions
**GitHub Discussions** at `https://github.com/lfnovo/open-notebook/discussions` hosts conversations about design principles, workflow architecture, and community ideas. The [`CONTRIBUTING.md`](https://github.com/lfnovo/open-notebook/blob/main/CONTRIBUTING.md) file and [`docs/7-DEVELOPMENT/contributing.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/7-DEVELOPMENT/contributing.md) cite this space for debating implementation strategies and refining feature specifications before committing code.
### Contributing Code Through Pull Requests
Active development happens through **Pull Requests** at `https://github.com/lfnovo/open-notebook/pulls`. Contributors should discuss significant changes in Discord or Discussions first, as noted in the contribution guidelines, then submit PRs for maintainer review and iterative refinement.
## Documentation and Self-Service Resources
The repository maintains extensive documentation that cross-references community channels throughout. The [`docs/index.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/index.md) file serves as the central hub, repeatedly pointing users to Discord for support. The [`CONTRIBUTING.md`](https://github.com/lfnovo/open-notebook/blob/main/CONTRIBUTING.md) guide provides contribution workflows while directing questions to Discord for real-time clarification. These documentation layers ensure users exhaust self-service options before escalating to community channels.
## Programmatically Embedding Community Links
Developers building applications on top of Open Notebook can expose support channels directly in their user interfaces and API documentation.
### React Component for Support Links
```tsx
// Example: Adding a βGet Helpβ button in the frontend (React/Next.js)
import Link from 'next/link';
import { Button } from '@/components/ui/button';
export default function HelpBanner() {
return (
Need assistance?
);
}
```
### FastAPI Endpoint Documentation
```python
# Example: Adding a help link to a FastAPI endpoint description
from fastapi import APIRouter
router = APIRouter()
@router.get(
"/status",
summary="Health check",
description=(
"Returns service health. "
"If you encounter problems, join our Discord: "
"https://discord.gg/37XJPXfz2w or open a GitHub issue."
),
)
async def status():
return {"status": "ok"}
```
### Markdown Documentation Snippet
```markdown
## Need Help?
- **Live chat:** Join our Discord server π
- **Report a bug / request a feature:** Open an issue on GitHub π
- **Discuss ideas:** Use GitHub Discussions π
```
## Summary
- **Discord** at `https://discord.gg/37XJPXfz2w` provides immediate, real-time community support for Open Notebook users.
- **GitHub Issues** track bugs and feature requests, while **Discussions** host architectural debates and design conversations.
- **Pull Requests** facilitate code contributions with maintainer review and iterative feedback.
- Documentation in [`README.md`](https://github.com/lfnovo/open-notebook/blob/main/README.md), [`docs/index.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/index.md), and [`docs/6-TROUBLESHOOTING/quick-fixes.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/6-TROUBLESHOOTING/quick-fixes.md) consistently reference these channels for comprehensive support.
- Developers can embed support links directly into React components, Python API documentation, or Markdown guides.
## Frequently Asked Questions
### How do I get immediate help with Open Notebook?
Join the Discord server at `https://discord.gg/37XJPXfz2w`. This is the fastest channel for troubleshooting installation issues, workflow questions, and configuration problems, as documented in [`README.md`](https://github.com/lfnovo/open-notebook/blob/main/README.md) and the troubleshooting guides under `docs/6-TROUBLESHOOTING/`.
### Where should I report a bug in Open Notebook?
Submit bug reports to `https://github.com/lfnovo/open-notebook/issues`. The Issues tracker provides structured templates for reproducible errors and allows maintainers to assign priorities, add labels, and track fixes through the development cycle.
### Can I contribute to Open Notebook without writing code?
Yes. You can participate in **GitHub Discussions** to refine feature ideas, improve documentation through pull requests, or help other users in the Discord community. The [`CONTRIBUTING.md`](https://github.com/lfnovo/open-notebook/blob/main/CONTRIBUTING.md) file and [`docs/7-DEVELOPMENT/contributing.md`](https://github.com/lfnovo/open-notebook/blob/main/docs/7-DEVELOPMENT/contributing.md) outline non-code contribution pathways including documentation improvements and community support.
### Should I discuss feature ideas before opening a GitHub issue?
Yes. The [`CONTRIBUTING.md`](https://github.com/lfnovo/open-notebook/blob/main/CONTRIBUTING.md) guide recommends using **Discord** or **GitHub Discussions** to discuss contributions and feature ideas before opening an issue or pull request. This preliminary conversation ensures alignment with project maintainers and prevents duplicate efforts.