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

Dashboard & Backend: Search configuration #11533

Open
ericholscher opened this issue Aug 9, 2024 · 5 comments
Open

Dashboard & Backend: Search configuration #11533

ericholscher opened this issue Aug 9, 2024 · 5 comments
Labels
Needed: design decision A core team decision is required

Comments

@ericholscher
Copy link
Member

Currently we have Search as an Addon that you can enable/disable. However, we should likely bring "Search" to a top-level setting in the project dashboard admin, and allow people to enable or disable it there for the whole project.

This would allow us to remove the files from the search index when the user disables search, and also remove it from site search, search API, and other places where we're exposing the search results.

@ericholscher ericholscher changed the title Dashboard & Backend: Disable search configuration Dashboard & Backend: Search configuration Aug 9, 2024
@humitos
Copy link
Member

humitos commented Sep 12, 2024

I'm not sure if this is super related to readthedocs/ext-theme#293, but since @agjohnson were asking about new potential settings, I'm pinging you here.

@agjohnson
Copy link
Contributor

agjohnson commented Sep 12, 2024

For purging search specifically, I would surface this in the version listing menu:

image

Or project listing menu if we can only manage a project level purge.

I do see how having a more top level project admin for some of the addons could make sense for some cases though, but I'd still probably keep addons specific configuration under the Addons admin panel either way. It would be confusing to split up addon settings like described here if we don't also have a top-level Flyout settings too -- that is, some addons configuration is top-level, some is under Addons.

Perhaps the Addons admin panel should be called something more user facing, like Documentation features -- this might help make our current admin structure more obvious.

@agjohnson agjohnson added the Needed: design decision A core team decision is required label Sep 12, 2024
@ericholscher
Copy link
Member Author

I think we originally created this issue because we were creating a bunch of search indexes that nobody was ever querying. If we treat turning off search in Addons as disabling search indexing completely, this could work well. I think there are also some other search configuration options, like whether to include subprojects by default, but that is also mostly about the Addons UX.

@humitos
Copy link
Member

humitos commented Sep 17, 2024

If we treat turning off search in Addons as disabling search indexing completely, this could work well.

If go this direction, we need to consider that enabling/re-enabling search will need to trigger a search re-index for all the active versions of that project. Maybe not an issue, but something to consider.

Also, search is enabled by default --which seems to be a good default to me. I don't think we will save too much by doing it opt-out.

@ericholscher
Copy link
Member Author

Yea, reindexing is definitely something we'd need to build if we made it able to turn off. I think that's probably good though. There's a bunch of people not using our search, so it would be good to save the resources of indexing if we can, but perhaps outside of the scope here? 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants