Repository Guide

Cloudberrie organizes source code into independent repositories, each with a clearly defined responsibility. This keeps deployments isolated, simplifies maintenance, and enables parallel development.

Repository Structure

Repository	Purpose
cb-manual	Internal documentation and operational knowledge
cb-website	Cloudberrie public website
cb-studio-board	Internal operations platform

Additional product repositories will be added as new products mature.

Standard Branches

Every production repository follows the same branching strategy.

Branch	Purpose
main	Production
staging	Release validation
develop	Active development
feature/*	New features
fix/*	Bug fixes
hotfix/*	Production emergency fixes

Repository Standards

All repositories should:

Include a README
Include a LICENSE (when applicable)
Use consistent branch naming
Follow semantic commit messages
Ignore build artifacts
Protect the main branch
Use Pull Requests for merges into shared branches

Local Workspace

Repositories are maintained inside the Cloudberrie Projects workspace.

Example:

Projects/
├── cb-manual
├── cb-website
├── cb-studio-board
├── eventlumi
└── aifa

The workspace allows multiple repositories to be opened simultaneously in Visual Studio Code.

Repository Ownership

Each repository should have:

Product Owner
Technical Owner
Deployment Environment
Documentation
Issue Tracking

Best Practices

Keep repositories focused on a single purpose.
Avoid unrelated changes in the same commit.
Keep documentation updated alongside code changes.
Merge through the standard promotion workflow.