To remove the "noise" associated with the project, I suggest disabling the following unused features if it still applies:
Go to General settings and disable the Wiki, Projects and Discussions tabs
If empty or unused, hide Releases and Packages section on the right side
Rational
It is just to simplify things.
For example, if user support is provided via a forum then it is better to turn off Discussions here, so that there is no need to monitor two user support sites, but only one.
If Releases and Packages are not used, so it is cleaner to hide them (to indicate that it is not the way how we manage releases and packages).
Projects feature is rarely used in general and this repository does not use it either. If the user clicks on Projects then an empty page is s displayed. It is better to not display the heading at all, to save the extra two clicks for users exploring the project.
Wiki on Github is meant to be a lighter weight tool for documentation. The issue is that it is too limited, for example contributors either can make changes directly (without pull request) or they cannot make changes at all. It also lead to write redundant content, since Github quite nicely renders markdown pages in the main repository. For small projects it is simpler and more consistent to keep all documentation in markdown files in the main repository.
lassoan
commented
1 year ago
> Reduce noise
@tavaughan @Sunderlandkyl @lassoan
To remove the "noise" associated with the project, I suggest disabling the following unused features if it still applies:
Wiki,ProjectsandDiscussionstabsReleasesandPackagessection on the right sideRational
It is just to simplify things.
For example, if user support is provided via a forum then it is better to turn off
Discussionshere, so that there is no need to monitor two user support sites, but only one.If
ReleasesandPackagesare not used, so it is cleaner to hide them (to indicate that it is not the way how we manage releases and packages).Projectsfeature is rarely used in general and this repository does not use it either. If the user clicks onProjectsthen an empty page is s displayed. It is better to not display the heading at all, to save the extra two clicks for users exploring the project.Wiki on Github is meant to be a lighter weight tool for documentation. The issue is that it is too limited, for example contributors either can make changes directly (without pull request) or they cannot make changes at all. It also lead to write redundant content, since Github quite nicely renders markdown pages in the main repository. For small projects it is simpler and more consistent to keep all documentation in markdown files in the main repository.
Co-authored by @lassoan
This comment was adapted from my GitHub saved replies, it is licensed under a Creative Commons Attribution 4.0 International License and you were welcome to reuse it.