Organization wide Wiki

[ariG23498]

It would be great if we could have an organization wide wiki. We use solutions like Notion an Google Doc at the moment. It would be great if could just have an organization wide wiki where people could go and note things down.

At the moment GitHub has wikis for each repository, which is useful too, but it comes with too many clicks to navigate to the wiki for all of our members.

Hope I could communicate my concers well!

TIA!

[michael-hawker]

Yeah, we'd like to use something like this as well. Right now our plan is to just have a repo for the wiki and push it out to the other repos' wikis. But it'd also just be nice to have something we could share all-up and then specific wikis for each project instead.

[shmeadyy]

Hey @ariG23498! 👋🏼 I'm a PM for GitHub investigating feature requests for wikis, and I was curious about this particular request. As you may know, we've shipped org-level READMEs, both for public consumption and for member-only consumption. Does the README satisfy this sort of request? If not, what about an organization wide wiki would be more suitable? Thanks!

[p0fi]

@shmeadyy Great to see this feature request on GitHub! I fully support this idea and believe it would be a valuable addition to GitHub. Looking forward to seeing it implemented soon.

[erichhannan]

I really like this idea of having a Wiki tab at the top level organization, where documentation about common practices can be shared across projects / repos. I landed on this thread after Googling to see if this was possible today, and I just can't find the Github org setting.

@schmeadyy said

what kinds of 'org-level documents' you mean, like what would qualify as an org-level document?

One example would be a documented "menu" of versioning schemes that define a common process for releasing and tagging the code in a particular repo. Our repositories use either 1) semantic versioning, or 2) sequential numeric versioning, with an optional add-ons of date/time based information or "build number" information in each version. It would be nice to define the menu of acceptable release naming/tagging conventions at the organizational level, have wiki page(s) for it at the organizational level, and then refer back to the common process document from the README file and/or wiki page for each repository. Right now, we end up storing the common documentation items in G docs or our intranet, and link from Github out to other tools.

I can imagine using the shared wiki for documenting other shared policies and procedures about code management that need to be adopted across all projects. For example, coding standards, requirements for release cadence, etc.

[bazzilic]

Hey @shmeadyy any updates on this?

[agneszitte]

Hello @shmeadyy any update on this issue, please? I would really like also on my side to have the possibility to have an org-level wiki. I would like to share with my team multiple pieces of documentation that are not related to a specific repo but more for general maintenance guidelines or other details and the org-level ReadMe (member-only) is not enough for that.
Thanks in advance for the feedback!

[dorschmeister]

This would be useful for our team as well for shared documentation that is not specific to a repository.

[SpBills]

Any update on this feature? We need a central place for procedure documentation and this would be the perfect thing for our organization.

Org-wide READMEs don't satisfy this because they are one page and not sufficient for multiple documents.

Our current solution is just to create a separate repo with a bunch of markdown files but this doesn't give us any nice features that a Wiki should.

[ispyhumanfly]

This solution is just not good enough. :(

[ispyhumanfly]

Even simply "Team Wide" wiki's would be really great.

[vijaystroup]

Looking for something like this as well.
A GitHub alternative of Confluence that has scoped permissions to a team but can be marked public to allow other teams to view it.
Perhaps something for GitHub Enterprise.

[cgaege]

@shmeadyy I would also love to see an org-level wiki. We're looking for a place to store org-wide documents like architecture documentation etc. that don't really fit into a single org-level README.

Our current approach is to create a dedicated repo within our org that only contains the wiki.

[PrimeDominus]

This would be really useful for us,

[agneszitte]

Still waiting on something like this, please. To have something where we could share general information across the organization.

(And additionally if possible, even if the wiki is available org-wide, to have the ability to choose to have some pages visible for public only and some for private only).

[GraphtyLove]

Same request here!