We love open source, and we’re thrilled that you want to help make xyOps even better! This document explains how to work effectively with the xyOps team and where your efforts can have the biggest impact.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/pixlcore/xyops/llms.txt
Use this file to discover all available pages before exploring further.
Before You Open a Pull Request
If you have a great idea for a new feature, please:Open a GitHub Issue
Create a new issue to describe your idea.
We generally prefer to design and implement new features in-house, but we’re very responsive and regularly integrate popular feature requests quickly. Your feedback shapes the roadmap!
Accepted Contributions
There are plenty of valuable ways to contribute:Bug Fixes
Small, well-scoped fixes are welcome! Requirements:Code Quality
Code Quality
- Your PR should clearly describe the issue and the reasoning behind your change
- All unit tests must pass (
npm test) - Follow our code style (see the Development Guide)
- Commits must be signed off (DCO) and GPG-signed
Testing
Testing
- Add tests for your fix if applicable
- Run the full test suite before submitting
- Ensure no regressions are introduced
Security Issues
Instead, follow the responsible disclosure process described in our Security Guide. Contact Methods:Localization
We’re preparing a formal localization process! If you speak languages other than English, we’d love your help translating xyOps once this is ready.
Plugin Development
How to Contribute Plugins:Read the Plugin Guide
See the Plugin Guide for full development and publishing details.
Register on Marketplace
Submit your plugin to the xyOps Plugin Marketplace.
Documentation Improvements
We happily accept PRs that improve our docs! Guidelines:Writing Style
Writing Style
- All documentation lives in
/docs - Follow the writing style in the Development Guide
- Use clear, concise language
- Include practical examples where appropriate
Images & Diagrams
Images & Diagrams
- Screenshots/diagrams should be PNG or WebP (lossless)
- Include proper alt-text for accessibility
- Keep file sizes reasonable
Spread the Word
If you enjoy xyOps, help us grow the community:Social Media
Social Media
Community Support
Community Support
- Participate in GitHub Discussions
- Help out new users with their questions
- Share your workflows and recipes
Video Content
Video Content
- Subscribe to our YouTube Channel
- Leave likes on videos you enjoy
- Share tutorials with your team
Development Guidelines
Technical Stack
| Component | Technology |
|---|---|
| Runtime | Node.js LTS |
| Language | Plain JavaScript (no frameworks) |
| Testing | pixl-unit |
| License | BSD-3-Clause |
Setup
For code style and setup details, see the Development Guide. Quick Start:Code Style
JavaScript Conventions
JavaScript Conventions
- Use tabs for indentation
- Follow existing naming conventions
- Add comments for complex logic
- Keep functions focused and small
Commit Messages
Commit Messages
- Use clear, descriptive commit messages
- Reference issue numbers when applicable
- Sign commits with DCO (Developer Certificate of Origin)
- GPG-sign all commits
Pull Request Process
Code of Conduct
All participants are expected to follow our Code of Conduct. Core Principles:- Be respectful and inclusive
- Welcome newcomers and help them learn
- Focus on constructive feedback
- Assume good intentions
- Foster a welcoming community
Contribution Ideas
Not sure where to start? Here are some ideas:Good First Issues
Good First Issues
- Look for issues tagged “good first issue” on GitHub
- Fix typos or improve documentation clarity
- Add examples to existing docs
- Write tutorials or how-to guides
Plugin Ideas
Plugin Ideas
- Integration with popular services (Slack, Discord, etc.)
- Cloud provider integrations (AWS, Azure, GCP)
- Monitoring and alerting plugins
- Custom trigger plugins for specific use cases
Documentation Needs
Documentation Needs
- More practical examples and recipes
- Video tutorials and screencasts
- Architecture diagrams
- Translation to other languages
Getting Help
Need help with your contribution?Community Support
Community Support
- Ask in GitHub Discussions
- Check existing issues for similar questions
- Join our community channels
Technical Questions
Technical Questions
- Review the Development Guide
- Check the API documentation
- Look at existing code for examples
Recognition
We value all contributions, big and small:- Bug fixes: Mentioned in release notes
- Plugins: Featured in the Marketplace
- Documentation: Credited in commit history
- Security reports: Credited in security advisories (if desired)