Ways to contribute
We welcome contributions to the install.md specification and ecosystem. Here are some ways you can help:Share examples
Have you created an install.md file for your project? Share it with the community!Submit an example
Add your install.md file to the examples page by opening a pull request on GitHub.
Improve documentation
Help make the specification and guides clearer:- Fix typos or unclear explanations
- Add missing examples or use cases
- Improve the format specification
- Translate documentation to other languages
Build integrations
Create tools that support install.md:- CLI tools for executing install.md files
- IDE extensions for VS Code, IntelliJ, etc.
- Browser extensions for one-click installation
- Package manager integrations
- Testing frameworks for install.md files
Share your integration
Let us know about your integration by opening a discussion or pull request.
Participate in discussions
Join the conversation about the specification:- Propose improvements to the format
- Share use cases and patterns
- Report issues or ambiguities
- Help answer questions from other users
Getting started
Fork and clone
- Fork the install-md repository
- Clone your fork:
Set up development environment
For documentation changes:-
Install the Mintlify CLI:
-
Start the development server:
- Open http://localhost:3000 to see your changes live
Make your changes
- Documentation files are in
.mdxformat - Examples go in
essentials/examples.mdx - Format specification is in
essentials/format.mdx - Integration guides are in
essentials/integration.mdx
Submit a pull request
-
Create a new branch:
-
Make your changes and commit:
-
Push to your fork:
- Open a pull request on GitHub
Contribution guidelines
Documentation style
- Use clear, concise language
- Include examples for complex concepts
- Use Mintlify components (Cards, Columns, etc.) for better UX
- Test all code examples
- Keep examples realistic and practical
Example submissions
When submitting install.md examples:- Include the full install.md file
- Add context about what the software does
- Mention any special considerations
- Ensure it follows the format specification
- Test it with an AI agent before submitting
Code contributions
For integration tools and utilities:- Include tests
- Add documentation
- Follow existing code style
- Ensure cross-platform compatibility where applicable
- Include installation and usage instructions
Specification changes
Proposing changes to the install.md specification requires more discussion:- Open a GitHub Discussion first to gauge interest
- Explain the problem you’re trying to solve
- Provide examples of how the change would work
- Consider backward compatibility
- Wait for community feedback before submitting a PR
What makes a good specification change
- Solves a real problem: Based on actual use cases, not theoretical needs
- Maintains simplicity: Doesn’t overcomplicate the format
- Backward compatible: Existing install.md files still work
- Clear benefits: The advantages outweigh the complexity
- Implementable: AI agents can reasonably support it
Community standards
We’re committed to providing a welcoming and inclusive community:- Be respectful and considerate
- Welcome newcomers and help them get started
- Give constructive feedback
- Focus on what’s best for the project
- Show empathy towards other community members
Recognition
Contributors will be:- Credited in the project documentation
- Mentioned in release notes for significant contributions
- Added to the contributors list
- Celebrated in community discussions
Questions?
GitHub Discussions
Ask questions and discuss ideas with the community.
Issues
Report bugs or request features.
Example contributions
Here are examples of great contributions:Adding an example
Improving documentation
Proposing a format change
Thank you!
Thank you for contributing to install.md! Your help makes software installation more transparent, secure, and accessible for everyone.View all contributors
See everyone who has contributed to the project.