From Tobias (https://redhat-internal.slack.com/archives/C046BDT4ARE/p1699561247827319): 

 
We are close to being ready to move from our current search solution, named fusion to solr/hydra.
Currently we have a feature within our header endpoint that allows searches from the api-catalog site to pre-select the filter api-catalog. This is done with this parameter in the url: ?f=type~api_docs.When we move to the solr/hydra search we will need to change the functionality.
If possible, we will need to amend the header on your site to include this in the search form: <input type=“hidden” name=“documentKind” value=“api_catalog”>So it will look like:
<form action="/search" method="get">
<label for="pfe-navigation__search-label-universal">Search</label>
<input id="pfe-navigation__search-label-universal" name="t" type="text" placeholder="Enter your search term">
<input type="hidden" name="documentKind" value="api_catalog">
<button>Search</button>
</form>
This will allow the search spa landing page to show pre-selected api-catalog results.
Notes:
Because both search solutions are different this solution will need to be present at the new search go live date, if it is present before it will not break anything, but also won’t function.
The developers header api is now being used by other spa’s so we can’t hardcode this value, which is why we are hoping that you are able to add it to the render of the header on your site.
This is also dependent on the search index work being completed so the results are present within the search collection. * Does your team see any issues with implementing this change on your end? (no) 

• How quickly do you think your team could make this change? We’re currently planning to launch on 11/28. (by end of week Nov 13)