I was going thought the website ofi3wm, which is one of the best tiling Window manager in Linux that is known to have excellent code. It's mainly written by Michael Stapelberg.

I noticed some great points about the software design and its philosophy on the website and I think they are excellent and something we could learn from. I will point out the relevant parts out of it, which is more general in my opinion.

These are the core idea from their website:

• Only documented behavior is supported. Clear documentation is a requirement for contributions.

• Only add features which benefit many people, instead of going to great lengths to support rarely used workflows.

• Keep mental complexity low: once you know i3’s key features, other features should be easy to understand.

• Do not add further complexity when it can be avoided. We are generally happy with the feature set of i3 and instead focus on fixing bugs and maintaining it for stability. New features will therefore only be considered if the benefit clearly outweighs the additional complexity, and we encourage users to implement features using the IPC whenever possible.

Now, we adapt it to our DjangoCMS and it looks something like this:

To adapt this set of guidelines forDjangoCMS (an open-source content management system for building websites), we can refactor the language so that it aligns with DjangoCMS’s ecosystem and philosophy. Here is the updated version:

DjangoCMS Contribution Guidelines

1. Only documented behavior is supported: Clear and comprehensive documentation is a strict requirement for all contributions. Features or changes should be well-documented to ensure ease of use and consistency for all users.

2. Focus on features with broad benefits: Contributions should prioritize functionality that will benefit a wide audience rather than focusing on niche or rarely used workflows. This helps keep DjangoCMS streamlined and efficient.

3. Minimize mental complexity: Once users are familiar with DjangoCMS’s key features, additional features should be easy to understand and use. Maintain simplicity in both code and user experience to avoid overwhelming users.

4. Avoid unnecessary complexity: Do not introduce additional complexity when it can be avoided. DjangoCMS has a well-rounded feature set, and new features should be proposed only if their value clearly outweighs the increased complexity.

5. Encourage modular development: New features should be implemented via plugins, apps, or extensions wherever possible, instead of modifying the core. This encourages a modular approach, keeping the core CMS lightweight and maintainable.

6. Stability and maintenance first: Focus on fixing bugs, maintaining stability, and enhancing existing features before introducing new functionality. Stability is a primary goal for DjangoCMS, ensuring a robust platform for all users.

This version aligns with DjangoCMS's philosophy of modularity, simplicity, and stability, while ensuring contributions are clear and well-documented.