-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add Elasticsearch guide #128190
Add Elasticsearch guide #128190
Conversation
Co-authored-by: joemcelroy <joseph.mcelroy@elastic.co>
include cloud deployment link in UI
This comment was marked as outdated.
This comment was marked as outdated.
…bana into elasticsearch-integration
This comment was marked as outdated.
This comment was marked as outdated.
const client = queryString.parse(window.location.search).client; | ||
const languageExists = languages.some((language) => language.value === client); | ||
const [selectedLanguage, setSelectedLanguage] = useState( | ||
languageExists ? (client as string) : 'java' |
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.
I suggest moving the string cast to line 44
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.
Yeah, nice catch, useState should usually be higher. But in this case, it seems necessary, because I'm using the languageExists
variable that I define above. Or did I misunderstand something?
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.
Few minor changes. Thanks for helping out with this!
<EuiText size="s"> | ||
{i18n.translate('xpack.enterpriseSearch.overview.elasticsearchCard.description', { | ||
defaultMessage: | ||
'Design and build performant, relevant search-powered application or large-scale search implementations directly in Elasticsearch', |
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.
We either need to make this change...
'Design and build performant, relevant search-powered application or large-scale search implementations directly in Elasticsearch', | |
'Design and build a performant, relevant search-powered application or large-scale search implementations directly in Elasticsearch', |
...or make "applications" plural:
'Design and build performant, relevant search-powered application or large-scale search implementations directly in Elasticsearch', | |
'Design and build performant, relevant search-powered applications or large-scale search implementations directly in Elasticsearch', |
<div> | ||
<EuiButtonTo to={ELASTICSEARCH_GUIDE_PATH}> | ||
{i18n.translate('xpack.enterpriseSearch.overview.elasticsearchCard.button', { | ||
defaultMessage: 'Get Started', |
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.
To be consistent with our writing guidelines, this should be:
defaultMessage: 'Get Started', | |
defaultMessage: 'Get started', |
</ul> | ||
<EuiLink | ||
target="_blank" | ||
href="https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/introduction.html" |
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.
We should use the docsLink service for these URLs. It will future-proof these in case the URLs change. This goes for all links in this PR that start with https://www.elastic.co/guide/en/
.
{i18n.translate( | ||
'xpack.enterpriseSearch.overview.elasticsearchCloudId.manageApiKeysLink', | ||
{ | ||
defaultMessage: 'Manage API Keys', |
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.
defaultMessage: 'Manage API Keys', | |
defaultMessage: 'Manage API keys', |
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.
Changes LGTM, pending CI
Looks like it was fixed in `master`, but not in `current` docs. Since the PR is going to master, we could use the corrected link
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.
The additions in kbn-doc-links LGTM
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
⚪ Backport skippedThe pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Summary
This PR adds a new page to the Enterprise Search app with Elasticsearch guide:
And a new panel to get to this page:
The PR is quite big, but 90% of the code is just plain HTML built with EUI components. I recommend reviewing the whole diff and not look at individual commits.
Several things are intentionally skipped:
Checklist