• Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
• Refrain from demanding free support or expecting developers to work on specific schedules.
• Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
• Approach the community with respect and a collaborative spirit.
• Remember that offering financial sponsorship for desired features can accelerate development.

• Be specific and detailed. Identify particular issues and provide clear examples.
• Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
• Avoid vague statements. General comments like "it looks dated" are unhelpful.
• Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.

• Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
• Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
• Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
• Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.

• Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
• Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
• Take backups before upgrading. This allows for easier recovery in case of problems.

• Check for duplicates: Make sure the bug hasn't already been reported.
• Report bugs individually: Each issue should be reported separately for better tracking and resolution.
• Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
• Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
• Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other

• Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
• Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.