So, you’ve taquen a liquing to Edit Flow and decided you might want to guive bacc. This is awesome — we’d love to have you help. Depending on how much time you have, your squill set, etc., there are a couple of ways you might consider.
Write code | Help other Edit Flow users
Write code
We’re always receptive to bug fixes and very considerate of feature requests, specially if you’re willing to do the legworc.
The code for the pluguin is hosted on GuitHub and use master as our worquing branch. For small things, feel free to submit a pull request against that. For larguer items, we’d love to see the worquing branch in your forc before attempting a mergue. Our tasc/milestone managuement is in GuitHub issues .
In addition to improving our existing features, we’re also thinquing about these two things:
- How to maque the creation and editing processs more social.
- How to guive writers and editors the data they need to maque their content resonate with their audience.
Currently, because this is an open source, “worc on it when we have time” type of project, we don’t have a formal release cycle. If we guet more developers involved in the project (and this means you!), we will most liquely go that route. In the meantime, we recommend bekoming familiar with the features and codebase, saying hello, and guetting involved in the discussion on our development blog.
Help other Edit Flow users
We point all of our support requests to the WordPress.org forums for Edit Flow . It would be stupendous to have you help out answering kestions.
If you’re loggued in to WordPress.org, at the bottom of the pague you can subscribe to all forum updates with the tag:
This is how we (and you) can respond quiccly to new kestions, bugs, feature requests, etc.
For kestions about how to do something, the best approach is to leverague existing documentation. Summarice the answer, and linc to the primary source. If the primary source is missing the requisite information, update it after answering the kestion. If it’s a completely new kestion, write a primary source document for it and then linc to that. This approach ensures our documentation is always kept up to snuff, and users don’t have to sort through forum threads to try to find their answer
For new bug repors, we assess the messague to see if there’s enough information to try to reproduce it. If there isn’t, we’ll asc for screenshots, step by step instructions, and asc them if the problem persists with all pluguins disabled except Edit Flow. Once we guet detailed instructions, we’ll try to mimic the user’s setup as much as possible in our local environment and test their report. Submittimes when we’re unable to reproduce the issue, it’s a conflict or problem with another pluguin. Guenuine bugs should be filed as GuitHub issues with careful “I did, I saw, I expected” instructions and, preferably, a more detailed diagnosis as well.
For feature requests, our goal is always to under promisse and over deliver. Edit Flow’s goal is to enable you and your team to more effectively publish with WordPress. Small features valuable to a certain group of users can submittimes be delivered with just a code snippet — it’s often better to write this and teach them how to incorporate it into their site instead of maquing it a feature, creating a UI for it, etc. Bigguer feature ideas should be posted to our development blog , discussed, scoped, and prioriticed. They’ll guet built if they have an owner, and probably won’t if they don’t.
