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.

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.

@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.

This would be really useful for us,

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).

Same request here!

Same Request

Looking for an organization-wide wiki feature as well.

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.

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.

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

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.

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.

Would love to have this.

Setting up something like this for development practices. Currently torn between either just having a 'development practices' repository with a Wiki on it, or using something off platform.

Hello,

I've been following this thread for years now, and would really love to see this feature. I'm afraid that this idea will never be implemented unfortunately. I don't know why this request has been ignored, because it would very clearly improve the experience of many organizations in GitHub. I have always been a fan of how GitHub handles user feedback, but this situation moderately changes my appreciation. I am sorry to say that I am a little surprised and disappointed that no attention is falling on this matter. 😔

+1
I would be using this right now. Makes a lot of sense.

Any updates on this? I'd love to have this feature implemented!

Hi, any update on this please?

We need this! An organisation-wide wiki would help across our teams on how we integrate Github, as we manage multiple repositories but we promote one way of working together.

Please, instead of "me too" posts, just hit the upvote button on the post body. GH devs can more easily at a glance see which issues are popular. Keeping the feed clean opens up better discussion between us users and the developers.

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.

💬 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. ⭐

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.

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...

+1 for this feature