to get the question clear I need to talk about some history, and it’ll make the post long. thanks for reading it!
If you are familiar with open source software project, you’ve had seen a release document every while. one of the best examples is the one for discourse team. e.g. look at this post and the following replies by the team.
this type of documentation has several benefits, the most important one for the community side is building the trust.
if you’re familiar with scrum methodology, you may know about daily meetings where the team is describing what they’re on and what they have done. there exists also grooming and planning sessions.
These all help the team to be aware of everything about what’s going on. that is somehow equivalent to mastery to the overall picture as well as details, in my point of view.
now my questions are something like this:
is it a good idea to list steps regarding the building a community, assuming that the whole community can be like a team, or an open source content-builder?
if you also think it is, then what kind of a feature list can suits the community (please read point 1)?
point 1: It’s so much easier to list a feature list rather than a tactic list or marketing steps or other steps needed to build and maintain a community. but it’s still possible to do that.