Skip to content
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

[Manage data] Refine Mapping section #408

Merged
merged 7 commits into from
Feb 12, 2025

Conversation

wajihaparvez
Copy link
Contributor

@wajihaparvez wajihaparvez commented Feb 11, 2025

Closes #370
Preview here

Summary

This PR includes the following updates to the Mapping section:

  • Cleans up the Mapping page to give a brief overview and introduce the reader to concepts covered in the section
  • Cleans up internal and reference links according to the IA spreadsheet
  • Checks lift-and-shift pages within the section
  • Deletes one raw migrated file since it's not being used anywhere else

Note to reviewer: Please see my comment about a wonky formatting error in one of the lift-and-shift pages. Insight is appreciated 🙏

@wajihaparvez wajihaparvez self-assigned this Feb 11, 2025
@wajihaparvez wajihaparvez changed the title 370/mapping [Manage data] Refine Mapping section Feb 11, 2025
@@ -8,7 +8,7 @@ mapped_pages:
One of the most important features of {{es}} is that it tries to get out of your way and let you start exploring your data as quickly as possible. To index a document, you don’t have to first create an index, define a mapping type, and define your fields — you can just index a document and the index, type, and fields will display automatically:

```console
PUT data/_doc/1 <1>
PUT data/_doc/1 <1>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that the "1" doesn't render properly in this code block and in the bullet after. It seems to be formatted the same as other pages where it's rendering like it's supposed to. I tried to troubleshoot this but I'm at a loss. Would appreciate any ideas

Copy link
Contributor

@kilfoyle kilfoyle Feb 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wajihaparvez Good question! If you change "console" to "json" I think it'll work (I tried it locally and that did the trick). That is, it seems to prevent the Markdown build from interpreting the <1> as part of the code example.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @kilfoyle, that worked!

kilfoyle
kilfoyle previously approved these changes Feb 12, 2025
Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🦕
Very nice!

@wajihaparvez wajihaparvez merged commit cabe00f into elastic:main Feb 12, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants