Guidelines

moja global encourages open-source contributions. The contributors can refer to the following guidelines:

• Contributing
  • Before making a contribution
    • Join our communication Channels
    • Contributors Website
  • Ways to contribute to moja global
    • Review & Contribute Science Design
    • Suggest UI/UX Improvements
    • Contribute Translations
    • Coach or Train New Contributors
  • Answer user Questions
  • Organize moja global events/meetups
  • Are There Other Ways of Contributing?
  • After making your first contribution
    • Get credit for your contribution
    • Report Bugs, Provide Feedback or Request Features
    • Pick more complex issues to work on
    • Help other contributors take their first step
      • Reviewing contributions
      • Answering their queries
  • Mentor new contributors
  • Create beginner-friendly Issues
  • Code Contribution Best Practices
    • Commit Guidelines
    • Commit Message Guidelines
    • Developer Certificate of Origin
    • Code Style & Conventions
  • Writing Documentation
    • Documentation in the codebase
    • Documentation in Markdown files
  • Documentation (readthedocs)
  • Documentation in the repository wiki
  • Documentation in Google Docs-files
  • Documentation in PDF-files
  • Code Of Conduct
    • Contributor Covenant Code of Conduct
    • Our Pledge
    • Our Standards
    • Our Responsibilities
    • Scope
  • Enforcement
  • Attribution
• GitHub Workflow
  • GitHub Repository maintenance
    • Repository Creation
    • Setting up Labels for your repository
  • How to maintain a GitHub repository
  • Creating and maintaining Project Boards
    • Creating your first board
  • Adding issues/pull requests to your Project Board
  • Build project boards into your workflow
  • Bots and Integrations
    • All-contributors Bot
      • Usage
      • Contributing
    • Prose Bot
      • Usage
      • Configuration
    • Stale Bot
      • Usage
    • Merge Conflict Watcher
      • Contributing
    • Welcome Bot
      • Contributing
    • Auto labelled Bot
      • Contributing
  • Automated Checks for pull requests
    • Continuous Integration
    • Code Coverage Check
  • Code Quality Check
  • FLINT Architecture
  • FLINT Performance
  • Reviewing a contribution
    • General Guidelines for reviewing
    • Things to look out for in a pull request
      • Performance
      • Code Style and conventions
  • Documentation
  • Tests
  • Design
    • What to do if you are not sure
  • Manually testing a pull request
• Moja global documentation style guide
  • Purpose
  • Tools & Technologies
    • Accessibility
      • Image accessibility
      • Text accessibility
      • UI accessibility
      • Links accessibility
      • Multimedia accessibility
    • Style & Tone
      • Approaches to be considered
      • Approaches to be not considered
      • For user-based documentation
      • For developer-based documentation
    • Language & Grammar I: Abbreviations & Acronyms
    • Language & Grammar II: Articles
    • Language & Grammar III: Capitalization
    • Language & Grammar IV: Clauses
    • Language & Grammar V: Conjunctions & Contractions
    • Language & Grammar VI: Direct & Indirect Speech
    • Language & Grammar VII: Plurals
    • Language & Grammar VIII: Possessives