Tenor

Intelligent, flexible, on-demand and light-weight tool that simplifies and optimizes the work of software development teams.

Project Index

• tenor_web: Main web application source code (frontend & backend).
• tenor_docs: Documentation site built with Docusaurus. It includes contribution guidelines, technical references, usage tutorials, and internal architecture notes — everything needed to ensure smooth onboarding and long-term maintainability.
• diagrams: Collection of system diagrams and architectural overviews. These visuals illustrate the structure, data flow, and interactions across components of the Tenor platform.

🤝 How to contribute to Tenor

We welcome contributions! To keep things organized and maintain a clean history, please follow the workflow below when contributing:

🪴 Branch naming convention

All branches must follow this format:

personal/{yourUsername}/{mainFunctionalityOrChange}

• Use your GitHub username or identifier.
• Use camelCase to describe the main change or feature.

✅ Contribution flow

1. Create a branch:
   Use the naming convention described above.
2. Develop your feature or fix:
   Commit frequently with meaningful messages.
3. Open a Pull Request (PR):
   • Must be approved by at least one member of the core team.
   • The description should include images or videos of the new functionality, if possible.
4. Link related issues:
   If your PR addresses a specific issue, make sure to link it properly.
5. After merge:
   Delete the remote branch to keep the repository clean.