To integrate group memberships more fluidly into the community-building aspects of Discourse posts, it would helpful to have a short-cut for inserting the join group interface directly into any post.
For example, it could be a code added to the end of a group name, e.g. @volunteers_group:join. Whether the button appears as +Join or +Request to join or -Leave will depend on the users current membership and group security.
The button should be displayed with the group name, as well as a note indicating what priviliges joining that group offers, i.e. is it a public/private group; which categories have added visibility.
The feature would give administrators of projects the ability to bootstrap teams very efficiently.
I think the use case is around self service, the groups page is kind of hidden, it would be a fairly complex change permission wise to support the proposal though
There are three content streams being featured, but each attendee should pick only one to focus on. Select which group to join below. We are also looking for 5 jury members to choose winning projects. Apply if interested.
So you’re saying that there is already a method in the codebase for generating this link, contrary to @sam’s concern, and it’s mostly a matter of building a new UI around generating the link?
I think that “Stream 1…” example would still work pretty well if those “JOIN” buttons were appropriately styled and just linked to the group page. I strongly doubt you’d lose many people in the onboard funnel with that extra click.
Although far from a perfect equivalent, I do hate it when websites use that interactive “follow us” Twitter widget which asks me to follow them immediately instead of taking me to their Twitter stream so I can see if I’m actually interested in what they’re putting out.
Sort of, we should allow for /groups?only-show-group=bla which would be a very easy change and take away a ton of the current noise of simply linking to the groups page. (eg: what if there are 100 groups)
이 오래된 주제를 다시 꺼내 봅니다. 검색해 보았지만 좋은 옵션을 찾지 못했습니다. 우리는 사이트 설정의 대부분을 한 곳에 집중시키고 싶습니다.
예를 들어, 채팅봇이 @xyz 그룹을 언급할 때 알림을 받을지 여부를 선택하는 네이/노 선택 항목을 그룹 가입/탈퇴 핸들러와 연결하는 것입니다. groups/?showonly= 링크로 연결하는 것이 그 다음으로 좋은 방법이지만, 많은 사용자에게 '설정 그룹’에 '가입’한다는 것은 직관적이지 않습니다.