Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: How to update the grouping/navigation of the 'all communities' tab #162

Open
OASIS-OP-Admin opened this issue May 6, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@OASIS-OP-Admin
Copy link
Contributor

From Lily @ HL:

Grouping certain communities together in All Communities list:
If you want to nest the communities under parent communities (make a Board community nested as a child community of the parent community "Board of directors"), you can do this by using the nested tool in Admin>Community>Tools>Manage Nested Communities: Nested Communities

If you simply want the list of communities to display in separate sections on the page, I'd recommend using multiple "Communities List" widgets that each filter those specific communities. My recommendation is to use the community type to filter them but if not, you can also select individual communities. This will need to be updated manually each time you create a new community however.

@OASIS-OP-Admin OASIS-OP-Admin added the documentation Improvements or additions to documentation label May 6, 2024
@OASIS-OP-Admin
Copy link
Contributor Author

This has been an evolution and work in progress. Most -comment lists are nestled under the corresponding TC. We have several that I lumped under 'staff' because they are old or private groups.

Further work needs to be done on the visibility settings or changing the group affiliation to something not visible to members and public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant