Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add wiki page at organization level #7077

Open
Xumeiquer opened this issue May 29, 2019 · 20 comments · May be fixed by #32947
Open

Add wiki page at organization level #7077

Xumeiquer opened this issue May 29, 2019 · 20 comments · May be fixed by #32947
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@Xumeiquer
Copy link

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.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label May 31, 2019
@Xumeiquer
Copy link
Author

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

@lunny
Copy link
Member

lunny commented Oct 9, 2019

Nobody are working on this.

@Xumeiquer
Copy link
Author

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
Copy link
Member

@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
Copy link
Member

lunny commented Jan 29, 2020

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

@Xumeiquer
Copy link
Author

@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
Copy link

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

@mpiorowski
Copy link

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

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Aug 8, 2022
@lunny
Copy link
Member

lunny commented Aug 8, 2022

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

@Xumeiquer
Copy link
Author

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

@dinbtechit
Copy link

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

@Xumeiquer
Copy link
Author

Xumeiquer commented Nov 13, 2022

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
Copy link
Member

lunny commented Nov 14, 2022

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.

@louischopot
Copy link

Any updates on this issue ?

@erikhuck
Copy link

erikhuck commented Aug 7, 2023

@lunny @Xumeiquer @guillep2k Has there been any more progress on this since November 2022?

@Xumeiquer
Copy link
Author

Xumeiquer commented Aug 17, 2023

I tried several times to do it, but without a guide on how to modify/improve the code without impacting on the Gitea design is hard, at least for me.

If someone can point me on the right direction I'll will try again.

@yp05327
Copy link
Contributor

yp05327 commented Sep 17, 2024

As we have implemented org level profile. Then we can use the same repo's wiki as the org's wiki?
Then the problem can be simple, adding a tab which links to this repo's wiki.

@msi-tl
Copy link

msi-tl commented Oct 22, 2024

I am really looking forward to this feature!

@wxiaoguang
Copy link
Contributor

wxiaoguang commented Dec 22, 2024

Actually I see the easy and clear approach to do so, without touching the "wiki" code (just like yp05327 said)

It could be done like " Add Profile Readme for Organisations #27955 ": add a wiki in the "profile" repo, and show a tab (link) on the org's homepage.

Does it satisfy the requirement here?

@wxiaoguang
Copy link
Contributor

-> Add profile wiki to org home #32947

easier than I thought

@wxiaoguang wxiaoguang linked a pull request Dec 31, 2024 that will close this issue
@lunny lunny added this to the 1.24.0 milestone Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants