# Contributing To ProjectNotes

Thanks for your interest in improving ProjectNotes.

## Best Ways To Help

- Report bugs with clear steps, expected behavior, and actual behavior.
- Suggest enhancements that solve a real project-management workflow problem.
- Improve documentation, examples, and wording where something is unclear.
- Submit focused pull requests that solve one problem at a time.

## Before You Open An Issue

Please:

1. Search existing issues to avoid duplicates.
2. Use the issue form that best matches your request.
3. Include enough detail for someone else to understand the problem or idea without extra back-and-forth.

## Bug Reports

Helpful bug reports usually include:

- ProjectNotes version
- Operating system
- Steps to reproduce
- Expected result
- Actual result
- Screenshots, logs, or sample data when safe to share

If the issue involves plugins or a specific integration, mention that early in the report.

## Enhancement Requests

Enhancement requests are most useful when they explain:

- The workflow you are trying to support
- What is difficult today
- What a better experience would look like
- Any tradeoffs, constraints, or alternatives you have considered

The more grounded the request is in day-to-day project work, the easier it is to evaluate and prioritize.

## Pull Requests

Please keep pull requests:

- Small enough to review comfortably
- Focused on one feature or fix
- Consistent with the existing code style and structure
- Updated with documentation when behavior changes

When relevant, include:

- Screenshots for UI changes
- Tests for behavior changes
- Notes about platform-specific impacts

## Documentation Contributions

Documentation improvements are welcome, including:

- Missing setup details
- Better examples
- Clarified plugin behavior
- Screenshots or workflow explanations

## Code Of Conduct

Please keep feedback respectful, specific, and constructive. Clear, practical collaboration helps the project move forward.