Add warning in searchapps page

[ketkee-aryamane]

Linked to #3564
Adds a warning to the UI navigation instructions for Search apps.

[github-actions]

🔍 Preview links for changed docs

• solutions/search/search-applications.md

[kderusso]

Is this type of warning something we typically call out in our docs? I don't remember us adding warning for previous nav changes, including when we removed app search from the nav. I'll defer to @leemthompo if this is necessary or not.

[leemthompo]

Thanks, just some minor comments

[leemthompo]

We can add applies_to's to admonitions now, so we don't have to spell out the deployment stuff in prose.

See https://elastic.github.io/docs-builder/syntax/admonitions/#applies-to-information

[leemthompo]

Is this type of warning something we typically call out in our docs?

I think it makes sense because folks running pre 9.2 deployments will still have access to the feature. It differs from the App Search case, because App Search disappeared in a major bump that coincided with docs migration for 9.0. I'd say it's a 70/30 call, but not a huge difference either way :-)

The alternative would be to use applies_to's to say that the feature is available in 9.0-9.1 but unavailable in 9.2. Same message, but less visible and I think the callout edges it in terms of clarity.

[leemthompo]

Thanks @ketkee-aryamane

[ketkee-aryamane]

@kderusso
Could we also recommend users to use https://www.elastic.co/docs/solutions/search/search-templates instead of search apps in the warning?

[leemthompo]

Could we also recommend users to use https://www.elastic.co/docs/solutions/search/search-templates instead of search apps in the warning?

That's a good idea, much better than just an unavailable warning 👍

"We recommended building with search templates instead."

In fact we could also have this recommendation at the top of each page TBH.

[kderusso]

I'm a little on the fence for the redirect, because if people are using search applications for the endpoint then that won't be an applicable replacement.

[leemthompo]

I'm a little on the fence for the redirect, because if people are using search applications for the endpoint then that won't be an applicable replacement.

Right maybe if we are clear that this would be a recommendation for brand new users who haven't yet used any Search
Applications functionalities. But perhaps it's too messy either way.

[leemthompo]

@ketkee-aryamane I vote we merge this now as is, and we can revisit adding additional recommendations when the API conversation matures