Proposal: hide explore menu #630

New Issue

GiteaMirror · 2025-11-02T03:30:55-06:00

GiteaMirror commented

2025-11-02 03:30:55 -06:00

Originally created by @yusefmaali on GitHub (Apr 9, 2017).

In some situations, the explore page may not be needed.

It should be very useful to have a config settings to hide at all the explore menu entry.
Something very similar to (for example) "DISABLE_REGISTRATION", we may have a "DISABLE_EXPLORE_MENU".

Thank you!

Originally created by @yusefmaali on GitHub (Apr 9, 2017). In some situations, the explore page may not be needed. It should be very useful to have a config settings to hide at all the explore menu entry. Something very similar to (for example) "DISABLE_REGISTRATION", we may have a "DISABLE_EXPLORE_MENU". Thank you!

GiteaMirror added the type/feature issue/stale labels 2025-11-02 03:30:55 -06:00

GiteaMirror closed this issue

2025-11-02 03:30:55 -06:00

GiteaMirror commented

2025-11-02 03:30:56 -06:00

@strk commented on GitHub (Apr 9, 2017):

Are you aware of the custom templates feature ?
With that you could easily hide the menu (but the page would still
be available by having a direct URL).

@strk commented on GitHub (Apr 9, 2017): Are you aware of the custom templates feature ? With that you could easily hide the menu (but the page would still be available by having a direct URL).

GiteaMirror commented

2025-11-02 03:30:56 -06:00

@yusefmaali commented on GitHub (Apr 10, 2017):

This sounds pretty interesting.
Can you give some hints to look for more details?

@yusefmaali commented on GitHub (Apr 10, 2017): This sounds pretty interesting. Can you give some hints to look for more details?

GiteaMirror commented

2025-11-02 03:30:56 -06:00

@strk commented on GitHub (Apr 10, 2017):

On Mon, Apr 10, 2017 at 02:09:00AM -0700, Yusef Maali wrote:

This sounds pretty interesting.
Can you give some hints where to looks for more details?

Uhm, I see the documentation is scarce:
https://docs.gitea.io/en-us/customizing-gitea/

It would be great if you could help improving it:
https://github.com/go-gitea/docs/blob/master/content/doc/advanced/customizing-gitea.en-us.md

Basically you copy any template from the templates/ directory
into the custom/templates/ directory, and modify as you see fit.
For your case it'd be the templates/base/head.tmpl to be copied
and modified.

Looking forward for your contribution to add a template section to
the documentation ! :)

@strk commented on GitHub (Apr 10, 2017): On Mon, Apr 10, 2017 at 02:09:00AM -0700, Yusef Maali wrote: > This sounds pretty interesting. > Can you give some hints where to looks for more details? Uhm, I see the documentation is scarce: https://docs.gitea.io/en-us/customizing-gitea/ It would be great if you could help improving it: https://github.com/go-gitea/docs/blob/master/content/doc/advanced/customizing-gitea.en-us.md Basically you copy any template from the `templates/` directory into the `custom/templates/` directory, and modify as you see fit. For your case it'd be the `templates/base/head.tmpl` to be copied and modified. Looking forward for your contribution to add a template section to the documentation ! :)

GiteaMirror commented

2025-11-02 03:30:56 -06:00

@yusefmaali commented on GitHub (Apr 10, 2017):

sure!

I need to pass through a Golang tutorial, then I will contribute for sure!

@yusefmaali commented on GitHub (Apr 10, 2017): sure! I need to pass through a Golang tutorial, then I will contribute for sure!

GiteaMirror commented

2025-11-02 03:30:56 -06:00

@strk commented on GitHub (Apr 10, 2017):

I surely think it's worth passing the Golang tutorial, but will
note you don't need Golang expertise to provide documentation
patches (it's just text, markdown if you wish)

@strk commented on GitHub (Apr 10, 2017): I surely think it's worth passing the Golang tutorial, but will note you don't need Golang expertise to provide *documentation* patches (it's just text, markdown if you wish)

GiteaMirror commented

2025-11-02 03:30:57 -06:00

@yusefmaali commented on GitHub (Apr 10, 2017):

Of course, you're right. I thought I needed to run gitea from its sources. I'm seeing the compiled version is enough.

@yusefmaali commented on GitHub (Apr 10, 2017): Of course, you're right. I thought I needed to run gitea from its sources. I'm seeing the compiled version is enough.

GiteaMirror commented

2025-11-02 03:30:57 -06:00

@Spenhouet commented on GitHub (Oct 2, 2018):

This would be a needed feature. User case: Non admin users should not be able to see other users and other repositories. Not sure, but hiding the explore page (also sub pages) could solve that.

@Spenhouet commented on GitHub (Oct 2, 2018): This would be a needed feature. User case: Non admin users should not be able to see other users and other repositories. Not sure, but hiding the explore page (also sub pages) could solve that.

GiteaMirror commented

2025-11-02 03:30:57 -06:00

@lafriks commented on GitHub (Oct 3, 2018):

@Spenhouet just hiding menu won't solve that. Access should be controlled also when opening repository page and for that there is private repository setting. If it is set other users won't be able to see that repository

@lafriks commented on GitHub (Oct 3, 2018): @Spenhouet just hiding menu won't solve that. Access should be controlled also when opening repository page and for that there is private repository setting. If it is set other users won't be able to see that repository

GiteaMirror commented

2025-11-02 03:30:58 -06:00

@stale[bot] commented on GitHub (Jan 7, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 7, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:30:58 -06:00

@stale[bot] commented on GitHub (Feb 22, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 22, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 03:30:58 -06:00

@lesderid commented on GitHub (Jun 14, 2019):

Was this added? Seems like a sensible feature to have.

@lesderid commented on GitHub (Jun 14, 2019): Was this added? Seems like a sensible feature to have.

GiteaMirror referenced this issue

2025-11-02 11:47:59 -06:00