🐛 Bug: Search bar in header does not work on Guide pages

[waygeance]

Describe the bug

The search bar shown in the header on the Guide page does not work and returns no results, even for valid ecosystem entries. This search functionality only works correctly on the home page, but still appears on guide pages where it provides no value and can confuse users.

Screencast.from.2026-01-17.21-10-19.webm

• Home Page Screenshot:

• Guide Page Screenshot:

Steps To Reproduce

1. Go to: https://landscape.json-schema.org/guide#introduction

2. Use the search bar in the header (top-right).

3. Search for a valid term (e.g. segmentation,etc.).

4. Observe that no results are returned.

5. Go to: https://landscape.json-schema.org/

6. Search any org like RESTheart, etc.

7. Observe that search works correctly on the home page.

Expected Behavior

• Either:

  1. The search bar should work consistently on Guide pages, or

  2. The search bar should be removed/hidden on Guide pages if it is not intended to function there.

• Showing a non-functional search bar on Guide pages creates a confusing user experience.

Screenshots

Screencast.from.2026-01-17.21-10-19.webm

• Home Page Screenshot:

• Guide Page Screenshot:

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

[waygeance]

Hi @jagpreetrahi, can you please look into this, and if it looks good to you, I will raise a PR to resolve this issue.
Thank you : )

[Utkarsh-123github]

Hi @waygeance , thanks for raising this issue. This is a valid point.
In my opinion, the guides page should not have search bar, because there is very less amount of content. So, I think we can remove search bar from there.
Please raise a PR for this.

[waygeance]

Thanks @Utkarsh-123github boss, I will raise PR by night to resolve this issue, Thanks : )

[waygeance]

This behavior originates from Landscape2, so I can’t modify it directly here. I’ve opened an upstream issue that will resolve this once addressed: cncf/landscape2#911