Mixing a community configuration page, and list of action items to handle on the same page might be a bit much, and will be more difficult to get the ux design to work.

Maybe a separate moderation page with a list of items that have been reported and need actions taken on them would be first. And then another page just for moderator configuration items for a community.

being able to re-edit markdown would be nice and like other web forum systems

Right now the results returned only contain content_text and content_html. The already rendered html is ok for display only purposes but not useful as a format for something which will be used for editing later.

Returning content_markdown as well in the result, would be more useful to front ends that want to allow the user to re-edit their original submission formatted in markdown.

A server setting to require all member account creations to be approved by a moderator/administrator before having any posting/comment provides could be an important spam protection mechanism.

Any user can create communities, this could be an easy to exploit Denial of Service. Someone could create an account and pollute the whole server with a ton of bogus communities.