-
Notifications
You must be signed in to change notification settings - Fork 150
[E&A] Creates a page for guidance on when to use EIS and when to use ML nodes #3124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a note:
The new page has the hidden attribute, which means that the page won't be published until we remove the hidden attribute.
It will actually be published. But it won't be indexed by search engines, nor appear in the navigation. Meaning it will be accessible with a direct URL only while it's hidden.
@florent-leborgne Thank you for your note. I updated the PR description accordingly. |
We should try to not make this ML node v.s. EIS but instead have
|
Overview
Related issue: https://github.com/elastic/search-team/issues/11055 and #3008
This PR creates a blank page under the EIS section for the content that the referenced issue above requests. The new page has the
hidden
attribute, which means that the page won't be indexed by search engines, nor appear in navigation, until we remove thehidden
attribute. It will be available via a direct URL. It makes it easier to create content and contribute to it.