What's in a WordPress developer's toolkit?

Hello,

We run a WordPress network across a university and it's increasingly being used for mission critical work. I want to write a document for new and existing web developers at the university that provides us with an agreed toolkit for WP development, as well as outline an expected process of development, so as to ensure code that is pushed to our production servers is well written, well tested and well documented.

I'd be very grateful if any of you could tell me/point me to what tools you use for WP development e.g. essential plugins for debugging, unit tests, how you deploy code, what your dev environment consists of, whether you use Continuous Integration, and suggestions for what you'd expect to see a team of WordPress developers using in a large organisation running a WP network.

This would be not only very useful to us, but I'm really interested in learning more about other WP developer's tooling. If you want to write to me off-list, it's jwinn@lincoln.ac.uk

I will share the document when it's finished.

Thank you
Joss

  • PC
    • WPMU DEV Initiate

    Hello josswinn,

    Greetings and thanks for writing on the forums.

    Right now, I do not have much info on the questions posted by you. I would be in touch with my team and get someone look into this and provide you any info/updates they might have.

    Till then, stay tuned and thanks for being a great member of the community !

    Cheers
    PC

  • Aaron
    • CTO

    I really can't say much other than all you said is important. We're still in major flux currently regarding unit testing and deployment of code.

    Most of what we do is very siloed as we have one core developer assigned to each product, and only recently are we starting to have devs and sometimes designers work as a team on a plugin/theme. For that though it seems to be working just fine to work via shared svn and chat.

    For something large though like edublogs.org or this site, it is very important to have a test environment and a testing/rollout process in place. Avoid cowboy coding as much as possible (we're way guilty of that, especially the last 48 hours here :wink:.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.