| # Contributing to Gingiris Go Global |
|
|
| Thank you for your interest in contributing! This playbook is built from real-world experience and we welcome contributions that add practical value. |
|
|
| ## How to Contribute |
|
|
| ### Content Contributions |
|
|
| - **Case studies**: Real go-global stories with specific data points |
| - **Channel updates**: New platform strategies, algorithm changes |
| - **Tool recommendations**: Verified tools for specific go-global tasks |
| - **Translations**: Improve existing translations or add new languages |
| - **Corrections**: Fix outdated information or broken references |
|
|
| ### Process |
|
|
| 1. Fork this repository |
| 2. Create a feature branch (`git checkout -b improve/topic-name`) |
| 3. Make your changes |
| 4. Submit a Pull Request with clear description of what you added/changed |
|
|
| ### Guidelines |
|
|
| - **Be specific**: Include numbers, timelines, and real examples |
| - **Be actionable**: Every recommendation should be executable |
| - **Be honest**: Don't oversell strategies; include failure modes |
| - **Cite sources**: Link to original data when possible |
| - **Keep it concise**: Respect readers' time |
|
|
| ### What We Don't Accept |
|
|
| - Generic marketing advice without specific execution steps |
| - Promotional content for specific paid tools (unless genuinely best-in-class) |
| - Theoretical frameworks without real-world validation |
| - Content that contradicts the core philosophy (fix the bucket first) |
|
|
| ## Questions? |
|
|
| Open an issue or reach out to the maintainers. |
|
|
| ## License |
|
|
| By contributing, you agree that your contributions will be licensed under the MIT License. |
|
|
