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

Control excessive Kedro versions in search results #2980

Closed
astrojuanlu opened this issue Aug 28, 2023 · 8 comments · Fixed by #3030
Closed

Control excessive Kedro versions in search results #2980

astrojuanlu opened this issue Aug 28, 2023 · 8 comments · Fixed by #3030
Assignees
Labels
Component: Documentation 📄 Issue/PR for markdown and API documentation

Comments

@astrojuanlu
Copy link
Member

Description

Sometimes when I search content from the Kedro docs, too many versions appear:

image

Context

Ideally, only one version (the latest one) should be shown.

Possible Implementation

Read the Docs allows you to hide a version from search engines https://docs.readthedocs.io/en/stable/guides/deprecating-content.html#deprecating-versions however, doing so also hides the version from the flyout menu.

Possible Alternatives

Alternatively, we can create our own robots.txt file https://docs.readthedocs.io/en/stable/guides/technical-docs-seo-guide.html#use-a-robots-txt-file that disallows certain versions from search engines while leaving the flyout menu untouched. This would need a bit of maintenance over time.

cc @stichbury

@astrojuanlu astrojuanlu added the Issue: Feature Request New feature or improvement to existing feature label Aug 28, 2023
@stichbury stichbury added the Component: Documentation 📄 Issue/PR for markdown and API documentation label Sep 4, 2023
@stichbury
Copy link
Contributor

This has bothered me for a while too, and I did restrict some of the older versions in RTD for that reason, but figured the flyout needed to show most, if not all, recent versions. I like the idea of modifying robots.txt and also thinking about how we present versions when we come to customise the docs with our theme for the subprojects. Maybe there's a way to update in RTD to restrict visibility in the flyout, but then add a design element to allow access to all versions that's separate from the flyout for people that really want them?

@stichbury
Copy link
Contributor

I'm going to suggest we put this in the coming sprint as a task for engineering (maybe @SajidAlamQB ?) but it's not a high priority if we need to push it over to the next.

@astrojuanlu
Copy link
Member Author

Starting point: the automatically generated robots.txt https://docs.kedro.org/robots.txt

@stichbury
Copy link
Contributor

We will need to guide @tynandebold and @SajidAlamQB on which versions we want to index and which we want to hide. Do we want to be fairly proscriptive and have just these indexed:

  • 0.16.0
  • 0.17.0
  • 0.18.0
  • Latest, stable

Or be a bit more generous and index these:

  • 0.16.0
  • 0.17.0
  • 0.18.0,
  • 0.18.5 - 0.18.13
  • Latest, stable

@stichbury
Copy link
Contributor

I think we may as well be quite strict but it does depend how familiar people are with the flyout at the bottom left, if they want more versions. Can we change the RTD settings so the docs always load with the flyout open?

@astrojuanlu
Copy link
Member Author

Or maybe instead of .0, the latest ones from each minor version? Hence

  • 0.18.5 onwards
  • 0.17.7
  • 0.16.6
  • latest, stable

@stichbury
Copy link
Contributor

Sounds reasonable, probably more useful than just going with the initial versions of each major release. Let's do it!

@stichbury
Copy link
Contributor

stichbury commented Sep 5, 2023

I've changed my mind, and think we should now update robots.txt to just allow these for search indexing:

  • 0.18.5 onwards
  • 0.17.7
  • latest
  • stable

All the versions are still on the RTD site and accessible. Just not indexed for SERP presentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Documentation 📄 Issue/PR for markdown and API documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants