Add missing content and mapped pages #369
Conversation
colleenmcginnis
requested review from
florent-leborgne,
shainaraskas and
szabosteve
explore-analyze/machine-learning/anomaly-detection/ml-configuring-populations.md
Outdated
Show resolved
Hide resolved
|
Note: I will fix the errors in the morning. 😴 |
|
@colleenmcginnis Thank you for opening this. The pages included in this PR under |
|
no major concerns here (holding until the pr is ready for review to approve), but cc'ing @kosabogi for visibility because she is working on snapshot/restore |
@szabosteve I had a feeling that was the case. Can you please let me know which files include the duplicate content so we know where to redirect these links?
|
|
@colleenmcginnis I updated the table in your comment above. However, my PR that deleted the pages addressed the redirects hopefully correctly. Please let me know if I can help anyhow. Thank you! |
Closes [#369](elastic/docs-projects#369) Preview [here](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/464/manage-data/data-store/index-basics) ### Summary What I changed: - Combined content from the three mapped pages - Altered the heading structure to make sense of the added content and improve readability i.e.: divided the page into **H2: Index components** and **H2: Index management** + changed all other headings to H3 and moved them under the relevant H2 - Drafted a new **Manage component templates** subsection to be consistent with the UI/screenshots - Cut down extra descriptive content from subsections to limit this page to Index _basics_ only, but linked out to relevant pages to compensate. The additions to the Mapping page are from one of the raw migrated files that I think made more sense there than on Index basics - Deleted links to Enriching your data examples from the **Manage enrich policies** subsection because I don't think that's relevant to this page I'll delete the code comments after this is reviewed. @colleenmcginnis @kilfoyle let me know what you think of these decisions. I'm open to all insight/suggestions 😄
3 participants
Related to https://github.com/elastic/docs-projects/issues/412
I'm just making sure all old URLs that should be mapped are indeed mapped.
@shainaraskas: The deploy and manage pages included here shouldn't change -- they are just getting additional mapped pages in the frontmatter.
@florent-leborgne @szabosteve: There are a few new pages in the explore and analyze section. I'm not sure if you actually need them, but they were included via "All children" in the inventory. If they are duplicates of other content, you can just add the mapped page URLs to the appropriate page.
Let me know if you have any questions!