Start Here: How to Contribute to TeamBuilder

[RocketDelivery2]

Thank you for your interest in contributing to TeamBuilder.

TeamBuilder is an open-source project with a simple mission:

Help people build, join, maintain, and refill teams with less downtime and more participation.

You do not need to be an expert to contribute.

Ways to contribute

You can help with:

• C# backend development
• ASP.NET Core Web API design
• Entity Framework Core modeling
• Azure SQL design
• unit tests
• integration tests
• documentation
• frontend examples
• mobile app ideas
• UX flows
• API client examples
• common roster language design
• GitHub Actions
• Octopus Deploy planning
• issue triage
• discussions
• real-world use cases

Good first contribution areas

Good starting points include:

• improving README documentation
• adding unit tests
• reviewing API endpoint naming
• suggesting roster schema fields
• adding example JSON roster payloads
• improving validation messages
• creating sample frontend API calls
• writing use case examples
• identifying missing edge cases

Technical direction

The project is being designed around:

• ASP.NET Core Web API
• C#
• EF Core Code First
• Azure SQL Server
• clean architecture
• xUnit tests
• frontend-agnostic API contracts
• Octopus Deploy-ready configuration
• Development, QA, and Production environment separation

Before opening a pull request

Please make sure:

• the project builds
• tests pass
• secrets are not committed
• code is clear and maintainable
• APIs use DTOs instead of exposing database entities
• list endpoints avoid unbounded results
• new behavior is documented where useful

Suggested local checks

• dotnet restore
• dotnet build
• dotnet test

Not sure where to start?

Reply here with:

1. Your experience level
2. What area interests you
3. Whether you prefer code, docs, testing, design, product ideas, or community support

We will help identify a good starting point.

TeamBuilder is about teams, and contributors are part of the team.