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!

[jghiloni]

Some of us would love this if ONLY to get rid of Confluence 😆

[zachgitt]

@shmeadyy Any updates on this? I'd love org level wikis as well

[VinGarcia]

I think this would indeed be a great feature, as someone commented before, and for my use-case as well,this would allow some of us to get rid of Confluence or other external documentation tools.

One requirement though for my use case would be the possibility of making this Wiki public, because as mentioned before Wikis for private projects are also private and thus do not work as external documentation for customers and/or users, in the case of a Organizational level Wiki I would expect it to include the possibility of being public for reading.

I hope this gets implemented it would be really great.

[drewid]

Confused about the question about a README, as it is nothing like a Wiki. It's only a specifically targeted summary about a specific topic.

@shmeadyy Not having an organization-wide Wiki really makes for a disjointed offering, needing to have into other places instead of focusing our concentration on using GitHub for all technical and dev related items.

[shmeadyy]

Hi folks! I'm sorry to say that there isn't any initiative at the moment to prioritize Wikis. However, this feedback is super helpful for whenever the teams decide they're ready to move forward with the product again. I also am no longer on the Product Managing teams at GitHub so I won't be able to share any updates on this in the future, unfortunately!

[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!

[pehaada]

Same Request

[geonnave]

Looking for an organization-wide wiki feature as well.

[mohd-afeef-badri]

I fully support the idea of an organization wide Wiki. It would centralize our documentation, making it easier to find and maintain. This would enhance consistency, streamline access, and promote knowledge sharing across teams.

[anthoturc]

I'd appreciate this feature too. For now I am just using private repository to act as a wiki for the entire org. Has some drawbacks but seems to work for now.

[kcrandall]

I would agree look that this is needed. Look into other implementations like Confluence and Slab for inspiration. There should be Harmony between org level wiki and repo level wiki. You should be able to reference/link projext level wikis in the org style wiki. And easily search a wiki across the entire org

[jamesoleg]

Sounds like you're on the right track! A central repo for the wiki content is a good starting point.

While pushing it out to individual repos might work, a dedicated organization-wide wiki could be ideal for that "all-up" view you mentioned. It would definitely streamline access for everyone.

[richardfwashington]

Hi All

We would also love to see this feature added. We will create a docs repo with a wiki for now. But a shared org wide one for best practices etc would be ideal. Thanks.

[drewid]

Hit the upload button, but a org-wide wiki would be a very helpful and should be obvious feature.

There are many, many uses for it. It's common to have org-wide information that is applicable on more than just a repository level.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[drewid]

Not having an organization-wide Wiki really makes for a disjointed offering, needing to have into other places instead of focusing our concentration on using GitHub for all technical and dev related items.

[alan-cognitivo]

Completely agree with this.

[mariana-caldas]

So, we've been vouching for it since 2021? That would make a huge difference for small to medium-sized companies, allowing them to cut costs while maintaining everything in the same place...

[danrasmuson]

+1 for this feature

[andymarden]

God, have they still not done it yet? It's such a simple addition.

[zachgitt]

It's literally insane

[nwarwick]

Yep big quick win opportunity imo. Really surprised they haven't jumped on it yet.

[Dzivo]

:( still no update

[andymarden]

That's a shame given how trivial it is to implement, following existing patterns. But thanks. Bit of a catch 22 - see if you can guess why wiki usage does not have greater uptake. If it did, the team would probably prioritise it...

…

On 08/07/2025 at 21:20, Laura Thorson ***@***.***> wrote: Hi folks! I'm sorry to say that there isn't any initiative at the moment to prioritize Wikis. However, this feedback is super helpful for whenever the teams decide they're ready to move forward with the product again. I also am no longer on the Product Managing teams at GitHub so I won't be able to share any updates on this in the future, unfortunately! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[Leomv55]

Our team is also looking for this feature. It will help us to keeps everything inside GitHub itself than checking multiple applications. Also, proper markdown support is not in other applications.

Hopefully, they will implement this soon.

[23tux]

+1 from our side!

[mia-riezebos]

+1

[dmitry-shechtman]

I'm guessing the powers that be are too busy shoving AI down our throats to meet some long-overdue feature requests.

[romerojunior]

+1 please