-
Notifications
You must be signed in to change notification settings - Fork 75
[Reference]: Fix Reference landing pages #1303
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
Comments
Per slack feedback, on the Cloud landing page “Cloud Hosted” should be “Elastic Cloud Hosted”. |
This PR updates the Kibana landing page. Relates to elastic/docs-content#1303 --------- Co-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>
This PR updates the Kibana landing page. Relates to elastic/docs-content#1303 --------- Co-authored-by: Florent Le Borgne <florent.leborgne@elastic.co> (cherry picked from commit 0fbb150)
This PR updates the Observability landing page. Relates to #1303
This PR updates the Security landing page. Relates to #1303 ## Notes for the reviewers I'm not sure what the correct link would be for [Detection Rules Overview](//detection-rules/docs/index.md). This page is a collection of links. --------- Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
This PR updates the ingestion tools landing page. Relates to #1303 --------- Co-authored-by: Lisa Cawley <lcawley@elastic.co>
This PR updates the data analysis landing page. Relates to #1303 --------- Co-authored-by: Lisa Cawley <lcawley@elastic.co>
As per Slack convo with @lcawl : |
Description
Revisit the reference landing pages to make sure that there are links from there to the relevant narrative docs (and vice versa).
- [ ] ECS reference- [ ] Search UIResources
More feedback to be taken into consideration while updating the landing pages.
Which documentation set does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
N/A
What release is this request related to?
N/A
Collaboration model
The documentation team
Point of contact.
@alaudazzi
@lcawl
The text was updated successfully, but these errors were encountered: