I'm willing to help with edits/content. Since we want to continue on Wordpress I just can't be an admin, I have absolutely zero experience with the admin of a Wordpress site. And very little experience with PHP. (But see the second part of the post for the git idea.)
I did write a handful (4-5) of seminars on GnuPG and another handful (2-3) about fiddling with memory (more-or-less reverse engineering). That said, I'm not a native speaker. I do use English as my main language for the past decade but sometimes I may still miss a subjective meaning of a phrase. On the other hand, I do not have bad English habits (e.g. your vs. you're) because I did not grow up in an English speaking country.
Should be good enough for an editor.
I'll take Andre Borie's point about github pages and extend it here.
Two things about Wordpress worry me:
We will likely need to create a new set of users and then link them to sec.SE in some way. So we will know who a person on the blog is on sec.SE.
Wordpress is famous for screwing up page revisions, and searching who exactly performed an edit is painful.
Both of these things can be solved by using a github repository. We already have an official field where we can add the link between SE and gihub (OK, it is on the SO profile but that is still SE), therefore we have the link between accounts.
The revision control of a git repo will allow us to know exactly when something was edited and by whom. Moreover, we can allow specific people (the editors) to be in charge of approving pull requests.
This isn't to say that the presentation of the blog cannot be on Wordpress, it only means that Wordpress should not be responsible for authenticating the contributors or keeping the post history. Instead, the bulk of work is managed in the git repository.
My personal blog takes its content from a git repository (it still has a database, but that only keeps more volatile things). Yet, that blog runs on Django (python), so it has an easy integration with git.