Skip to content

Fix stale docs search results opening client-side 404 pages #131

Description

@rmcdaniel

Problem

The published docs search returns legacy /docs/2.0/ results. Those paths have redirect HTML but no client-side route, so clicks previously rendered Page Not Found although direct visits worked.

Independently reproduced September 12 by searching waterline from https://durable-workflow.com/docs/monitoring/ and clicking the Cancel and Terminate result. All 47 unique returned paths had canonical counterparts in the current build.

Delivered

PR #132 uses the built-in Docusaurus replacement to canonicalize only the former version prefix. It is deployed, with actual live desktop/mobile search navigation verified and seven build-time normalization/URL regression assertions. Current paths, 1.x, queries and anchors are preserved.

Acceptance

  • Repair the legacy-prefix search navigation failure without a custom router.
  • Verify built and deployed browser clicks, including a narrow viewport and navigation through the indexed category to the Waterline API reference.
  • Refresh or replace the stale index so results match current stable pages/headings and preserve intentional 1.x search.

Remaining index work

The live index still uses prerelease titles, returns the removed Monitoring #installing-waterline heading, and does not directly return the current Waterline Operator API Reference page. Searching that exact title returns the category and referring pages instead.

Next: correct the existing crawler's canonical/version discovery and recrawl, then check results against current headings. If that service cannot be kept current, evaluate an established build-time Docusaurus search plugin. Do not build a custom crawler or coordinator. This follows active runtime reliability work; the reported click-to-404 defect is already repaired.

Related feedback checked separately

The fresh-install legacy tables are independently confirmed and tracked in workflow#513. Sampled maintainer-authored Waterline issue bodies/comments did not establish a specific broken repository-relative docs link; no historical records were edited speculatively.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions