Add wiki page at organization level

[Xumeiquer]

Some organizations has several projects that belongs to a big project, like those that have backend or server side and frontend or client.

That would be amazing to have a kind of wiki page for the organization so it would be unique entry point where the organization could explain the whole project and any other projects and finally each project will have its own documentation as usual.

Thanks.

---

Update: since Gitea has "org profile readme" feature (#27955 and #32872), there could be a pretty good workaround for this case:

Org admin could create wiki under their "org profile" or "org private profile", and use org profile readme to describe it and link the wiki to org's home page. It is more flexible than hard-coded wiki link.

[Xumeiquer]

Are there any news on this? any plan when is it going to be added?

[lunny]

Nobody are working on this.

[Xumeiquer]

I would like to help by adding this feature.

My idea is to add one wiki page at the organization level, which acts as a documentation entry point for further documentation on each repo wiki site, for instance.

Key points:

• The org admin will be able to enable o to disable the wiki page
• Org admin or any team admin will be able to edit the wiki page

How does it sound?

[guillep2k]

@Xumeiquer Thanks for your offer. I think most of the structure required for this functionality is currently supported by Gitea. Almost . IMHO, what needs to be done is:

• Provide a setting at the org level to set some repository as the wiki home.
• Set up a link to the wiki in the organization page.
• Support the wiki being public while other parts of the repository (code, issues, etc.) are not.

The tricky part is the last one, as changing the permissions structure require a lot of planning. #9787 will certainly help with this task when it's finished.

[lunny]

I think we can create a repository named <org_name>/_default.wiki.git and reverse the name _default.

[Xumeiquer]

@guillep2k I can start working on the first two bullet points and leave the last one until the #9787 will be finished. Thus the wiki repo at org level will be private for now.

@lunny I think it is a good approach.

[erikhuck]

@Xumeiquer Is there a way to have a wiki for an organization now? I can't find that option for my organization.

[mpiorowski]

Any updates on that issue? This would solve so much organization problems for us :)

[lunny]

The web URL could be <org_name>/-/wiki and the clone URL could be <org_name>.wiki.git.

[Xumeiquer]

I have some spear time and want to catch up on this.

[dinbtechit]

Any update on this? This is a pretty vital feature.

[Xumeiquer]

Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality.

What will be the best approach?

1. Reuse the code at the repository level and do any adjustment, if needed.
2. Or, duplicate the wiki code at the Org level.
3. Any other approach I am not aware of.

[lunny]

Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality.

What will be the best approach?

1. Reuse the code at the repository level and do any adjustment, if needed.
2. Or, duplicate the wiki code at the Org level.
3. Any other approach I am not aware of.

I think most code could be reused.