Welcome to Cursor Boston! This document will help you find the right resources and support for your needs.
Our Discord server is the best place for real-time help and community interaction.
Join us: discord.gg/Wsncg8YYqc
Discord is great for:
- Quick questions and answers
- Sharing what you're working on
- Connecting with other community members
- Getting help with development setup
- Discussing AI-powered development workflows
We host regular in-person and virtual events in the Boston area.
Event calendar: lu.ma/cursor-boston
Events include:
- Monthly meetups
- Workshops and tutorials
- Hackathons
- Speaker sessions
- Networking events
Visit our website for information about the community and upcoming events.
Website: cursorboston.com
-
Search existing resources first
- Check the Development Guide for setup, scripts, and troubleshooting
- Check our README for project overview and quick start
- Search existing issues for similar questions
- Review the API Reference for endpoint documentation
-
Ask on Discord
- Join our Discord server
- Post in the appropriate channel
- Provide context about what you're trying to do
-
Longer-form or architectural topics
- GitHub Discussions is not enabled for this repository. Use Discord for open-ended discussion, or open a feature request issue when you want a tracked proposal on GitHub.
Found a bug? Please report it!
- Check existing issues to avoid duplicates
- Use the bug report template when creating a new issue
- Include:
- Steps to reproduce
- Expected vs actual behavior
- Screenshots if applicable
- Your environment (OS, browser, Node version)
Have an idea for a new feature?
- Check existing issues to see if it's been proposed
- Use the feature request template when creating a new issue
- Include:
- Clear description of the feature
- Use cases and benefits
- Any implementation ideas
Do not report security vulnerabilities through public issues!
Please see our Security Policy for instructions on reporting security vulnerabilities.
Interested in contributing to the project?
- Never coded before? Start with Get Started (No Experience Needed) — plain language, AI tools do the work
- New to open source? Follow the First Contribution Guide for a step-by-step walkthrough
- Set up your environment with the Development Guide
- Read our Contributing Guide for policies and code style
- Check out good first issues
- Review our Code of Conduct
- Learn about our governance model
| Document | Description |
|---|---|
| README | Project overview and quick start |
| Get Started | Plain-language guide for complete beginners |
| Development Guide | Setup, scripts, troubleshooting, architecture |
| First Contribution | Step-by-step first PR walkthrough |
| CONTRIBUTING | Contribution policy and code style |
| API Reference | Full list of API endpoints |
| CODE_OF_CONDUCT | Community guidelines |
| SECURITY | Security policy |
| GOVERNANCE | Project governance |
| DCO | Developer Certificate of Origin |
| TRADEMARK | Brand usage policy |
| CHANGELOG | Version history |
| Documentation index | Which doc to read first |
| Supply chain & security automation | CI security signals and dependency tooling |
Email: hello@cursorboston.com
Use this for:
- General questions about the community
- Partnership inquiries
- Speaking opportunities
- Press and media
Email: hello@cursorboston.com
All reports are confidential. See our Code of Conduct for details.
Email: hello@cursorboston.com
See our Security Policy for the full disclosure process.
We're a volunteer-run community project. Here are our typical response times:
| Channel | Response Time |
|---|---|
| Discord | Within 24-48 hours |
| GitHub Issues | Within 1 week |
| Within 1 week | |
| Security Issues | Within 48 hours |
- Next.js Documentation
- Firebase Documentation
- Tailwind CSS Documentation
- TypeScript Documentation
- React Documentation
Thank you for being part of the Cursor Boston community!