Thank you for considering contributing to AkiraDocs! This document will guide you through the contribution process.
- Code of Conduct
- Legal Requirements
- Getting Started
- Development Guidelines
- Contributing Process
- Community and Support
This project follows our Code of Conduct. All contributors are expected to uphold these guidelines.
This project uses a dual-license model:
-
MIT License
- Applies to all code NOT in folders named 'enterprise' or prefixed with 'enterprise-'
- Allows free use, modification, and distribution
- Your contributions to MIT-licensed portions will be licensed under MIT
-
Commercial License
- Applies to all code in folders named 'enterprise' or prefixed with 'enterprise-'
- Owned by Cloud Code AI Inc.
- See LICENSE-ENTERPRISE.md for terms
- Contributions to enterprise portions require additional agreements
Directory Structure:
*/enterprise/* -> Commercial License
*/enterprise-*/* -> Commercial License
All other directories -> MIT License
For licensing questions, contact [email protected]
- All contributors must sign our CLA at cla-akiradocs
- We offer Individual CLA
- The CLA is required regardless of contribution size
- For corporate contributions, have your legal representative reach out to [email protected]
-
Fork and Clone
git clone https://github.com/your-username/akiradocs.git cd akiradocs
-
Setup Environment
npm install npm run dev
-
Create Branch
git checkout -b feature/your-feature-name
akiradocs/
├── components/ # React components
├── pages/ # Next.js pages
├── styles/ # CSS files
├── lib/ # Utilities
├── public/ # Static assets
└── tests/ # Test files
// Component Example
interface ButtonProps {
label: string;
onClick: () => void;
disabled?: boolean;
}
const Button: React.FC<ButtonProps> = ({ label, onClick, disabled }) => {
return (
<button
onClick={onClick}
disabled={disabled}
className="btn-primary"
>
{label}
</button>
);
};
- Use TypeScript for new components
- Follow existing code formatting
- Use Tailwind CSS where possible
- Write meaningful variable/function names
- Add comments for complex logic
-
Before Starting
- Check existing issues and PRs
- Discuss major changes in an issue
- Ensure CLA is signed
-
Development
- Write clear commit messages
- Add necessary tests
- Update documentation
- Follow style guidelines
-
Pull Request
- Fill out PR template
- Link related issues
- Add screenshots for UI changes
- Be responsive to review comments
- Join our Discord
- Read our Documentation
- Use GitHub Discussions for questions
- Report bugs via GitHub Issues
Contributors are recognized in CONTRIBUTORS.md and release notes.