Thank you for your interest in contributing to Scene Capability Engine! 🔥
We welcome translations to make Scene Capability Engine accessible to more developers worldwide.
-
Create Language File
- Copy
locales/en.jsontolocales/[language-code].json - Example:
locales/ja.jsonfor Japanese
- Copy
-
Translate All Strings
- Translate all text values in the JSON file
- Keep the JSON structure and keys unchanged
- Maintain emoji and formatting
-
Update Language Detection
- Edit
lib/i18n.js - Add detection logic in the
detectLocale()method:
if (envLocale.startsWith('ja')) return 'ja'; if (systemLocale.startsWith('ja')) return 'ja';
- Edit
-
Create Translated README
- Copy
README.mdtoREADME.[language-code].md - Example:
README.ja.mdfor Japanese - Translate all content
- Add language switcher at the top
- Copy
-
Update Main README
- Add your language to the "Supported Languages" section
- Add link to translated README
-
Test Your Translation
npm link sce --lang [language-code] init
-
Submit Pull Request
- Create a PR with your changes
- Include screenshots of the translated interface
- Describe what language you added
- Be Consistent: Use consistent terminology throughout
- Keep It Natural: Translate meaning, not word-for-word
- Preserve Formatting: Keep emoji, markdown, and code blocks
- Test Thoroughly: Test all commands with your translation
- Use GitHub Issues
- Include steps to reproduce
- Specify your environment (OS, Node version, etc.)
- Open a GitHub Issue with the "enhancement" label
- Describe the feature and its use case
- Explain how it aligns with the Ultrawork spirit
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
When contributing, embody the Ultrawork spirit:
- Never settle for "good enough" - Strive for excellence
- Continuous improvement - Iterate on feedback
- Persistent effort - Don't give up on challenging problems
Thank you for helping make Scene Capability Engine better! 🙏