One thing to consider for some of the community features indicated in your post is if it will be a Json transaction that an admin can do or if it will need the account owner to put the info into the community account metadata with an active key. Or mix of both.

For example we will have a couple features coming up that we are doing this method with the account metadata even though letting the admin make changes sure would be nicer for user experience specially if it's something that needs to be edited often.

Also community stats that deal with comments or rewards are problematic because it is largely a reflection on the individuals following and their ability to bring in comments and rewards and it is uncertain what the community had to do with it. Not saying we have to get rid of those stats but given better options those ones should be related way down in the list.

So I am in favor of stats that show a user what the community is actually doing.

• lifetime number of content posts
• recent number of content posts
• number of unique users posting content

Those seem to be directly related stats to what the community experience. It also indicates to the new user what they can expect after they follow the community (what will happen to their follow feed)