Thank you for your interest in submitting a feature request to ProcessWire. 👍
We manage these feature requests in this separate repository so that they don’t get mixed up with bug reports. It also enables us to maintain a collaborative team to help manage them. The following is a set of guidelines for contributing to this repository. These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to github@processwire.com.
- Please note that we generally avoid adding features that aren’t going to be used by at least 30 % of the ProcessWire audience. Often new features can be better accommodated with modules.
- If we close your feature request, this does not mean it won’t ever be implemented. It just means that we aren’t ready to implement it just yet. Closed feature requests aren’t ever deleted, so consider closed feature requests to just be on the back burner.
- Sometimes we will leave a feature request open for awhile to see how much interest it gains from others before we decide whether it should be implemented.
- Please do not submit bug reports, instead use the issues repository.
- Please do not use this repository for ProcessWire support, instead use the support forum.
- Check the Wishlist & Roadmap board in the forum.
- Perform a cursory search to see if the enhancement has already been requested. If it has, add a comment to the existing request instead of opening a new one.
Always include as many details as possible. There is an issue template which gets used automatically when you create a new feature request. Please use it as it contains all the information needed for a good feature request.
This will help maintainers and the community understand your feature request, comprehend the usefulness of it for the community, and get to a solution more quickly and efficiently.