While we were working on improving (sub)community visibility on our site, we realized there was no place to store a community charter/description. This is required on sites where you want to advertise available sub-communities to all of the site's users. The default subsite page shows only the name, which may be enough on small sites but probably won't be on large sites with diverse communities.
After looking into it a bit and discussing with a couple of people, I decided the easiest way to add this bit was to add a "description" field to the groups table. This is where join policy is stored and since this really IS the community (i.e., the application group associated with the subsite holds all members), it felt right.
Does that make sense? Anyone have any concerns about (or a better suggestion for) adding this to the toolkit?
