DEVdocs is a community-driven platform created to help developers discover, understand, and use applications, tools, and libraries more effectively. The strength of DEVdocs comes from the people who contribute their knowledge, experience, and time to make the platform better for everyone.

Whether you’re a developer maintaining an application, a contributor improving documentation, or someone reporting an issue, every contribution matters. These guidelines explain how you can participate, what kind of contributions we welcome, and how the review process works.

Our goal is to keep contributions simple, transparent, and accessible to developers of all experience levels.

How to Suggest Apps or Documentation

One of the core purposes of DEVdocs is to act as a shared space where developers can list and document their applications. If you have built an application, library, or developer tool that you believe others would benefit from, you are welcome to suggest it for inclusion.

Suggesting New Apps or Tools

To suggest a new application or tool:

• Open an issue on our GitHub repository.
• Provide the name of the application and a short summary of what it does.
• Describe the primary use case and the problem it solves.
• Mention the intended audience (for example: frontend developers, backend developers, mobile developers, DevOps engineers).
• Include links to the source code, official website, or existing documentation if available.

When suggesting an application, please make sure that:

• The project is actively maintained or in a stable state.
• The documentation is reasonably complete and understandable.
• The tool provides meaningful value to developers and is not purely promotional.

Once submitted, the DEVdocs team will review the suggestion. If needed, we may ask for additional details or clarification before approving the listing.

Suggesting Documentation Improvements

DEVdocs is not just about listing applications—it’s also about improving how developers understand and use them. You can contribute by enhancing existing documentation or suggesting improvements to content already published on the platform.

You can suggest documentation improvements by:

• Opening an issue on GitHub describing what needs improvement.
• Pointing out unclear sections, missing steps, or outdated information.
• Suggesting better explanations, examples, or structure.

Clear documentation benefits everyone, and even small improvements—such as fixing wording or reorganizing sections—are highly appreciated.

Improving Existing Documentation

If you want to make direct changes to documentation content, DEVdocs supports contributions through pull requests.

Making Documentation Changes

To contribute changes:

1. Fork the DEVdocs repository on GitHub.
2. Create a new branch for your changes.
3. Make your updates, ensuring clarity and accuracy.
4. Submit a pull request with a brief explanation of what you changed and why.

When making documentation changes, please keep the following in mind:

• Write in clear, simple language.
• Avoid unnecessary jargon where possible.
• Use headings and lists to improve readability.
• Ensure examples are accurate and easy to follow.
• Keep the tone professional and inclusive.

Documentation does not need to be perfect, but it should aim to be helpful, understandable, and approachable.

Reporting Issues

If you encounter a problem while using DEVdocs, reporting it helps us improve the platform for everyone.

What You Can Report

You can report:

• Bugs or broken functionality on the website.
• Incorrect, outdated, or misleading documentation.
• Broken links or missing references.
• Display or accessibility issues.
• Inconsistencies across documentation pages.

How to Report Issues

To report an issue:

• Open an issue on the DEVdocs GitHub repository, or
• Share details in the appropriate Discord channel.

When reporting an issue, try to include:

• A clear description of the problem.
• Steps to reproduce the issue, if applicable.
• Screenshots or links, if helpful.
• Information about your browser or environment, if relevant.

Clear issue reports help the team resolve problems more quickly and accurately.

Joining the Community Discussion

DEVdocs is more than just documentation—it’s a community. We encourage developers to engage with one another, share ideas, and collaborate.

Discord Community

Our Discord server is the best place to:

• Ask questions about DEVdocs.
• Discuss tools, apps, and best practices.
• Get feedback on ideas or contributions.
• Stay informed about platform updates.

Participation in discussions is entirely optional, but highly encouraged. Even asking questions or sharing feedback helps improve the platform.

Contribution Review Process

All contributions to DEVdocs are reviewed before being published. This review process exists to maintain quality, accuracy, and consistency across the platform.

What Happens After You Contribute

Once you submit a contribution:

1. The DEVdocs team reviews the submission.
2. We may request changes or additional information.
3. Once approved, the content is published or merged.

Reviews are conducted with the intent to improve content, not reject contributions unnecessarily. Feedback is provided constructively, and contributors are encouraged to iterate.

Content Quality Expectations

To ensure DEVdocs remains useful and trustworthy, we ask contributors to follow a few basic quality principles:

• Be accurate and honest about what your app or documentation provides.
• Avoid misleading claims or exaggerated descriptions.
• Respect intellectual property and licensing requirements.
• Do not submit plagiarized or copyrighted content without permission.
• Keep content relevant to developers.

These guidelines are meant to protect both contributors and users of the platform.

Inclusivity and Respect

DEVdocs is an inclusive space. We welcome contributors from all backgrounds, skill levels, and regions.

We expect all participants to:

• Communicate respectfully.
• Be open to feedback.
• Avoid harassment, discrimination, or abusive behavior.

Constructive disagreement is welcome, but personal attacks or harmful behavior are not tolerated.

Code of Conduct

By participating in DEVdocs—whether through content contributions, discussions, or issue reporting—you agree to follow our Code of Conduct.

Please review it here:
Code of Conduct

The Code of Conduct exists to ensure that DEVdocs remains a safe, respectful, and productive environment for everyone.

Final Notes

You don’t need to be an expert to contribute to DEVdocs. If you’ve learned something useful, discovered a better way to explain a concept, or built something others might benefit from, your contribution is welcome.

DEVdocs grows through shared knowledge, collaboration, and community effort. Thank you for helping make it better.