Skip to content

Poor search results on third-level headers #808

@genedan

Description

@genedan

Are you on the latest chainladder version?

  • Yes, this bug occurs on the latest version.

Describe the bug in words

Certain sections that should appear near the top of the search results either aren't listed in the query or are poorly ranked. For example, when looking for "grain", we should expect the section Triangle Grain at the top of the results, rather than the parent page for Triangle. The user would then have to navigate all the way down to the relevant section, but if they don't know the section actually exists, they might give up before reaching it.

Image

Even after querying the name of the section, the correct result is ranked 7th:

Image

How can the bug be reproduced?

Search for grain or another section marked with a third-level header, ### I suspect it might be a third-level header problem, but I'm not sure. We can update the description accordingly if the correct cause is found.

What is the expected behavior?

Triangle Grain should appear at the top of the search results.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Documentation 📚Changes to docstrings or the documentation site. No codebase changes.Effort > Moderate 🐕Mid-sized tasks estimated to take a few days to a few weeks.Impact > Moderate 🔶User-visible but non-breaking change. Treated like a minor version bump (e.g., 0.6.5 → 0.7.0).

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions