[DO NOT MERGE] Docs-content component of consolidating AI connector guides #3844
+8
−381
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Preview links for changed docs |
benironside
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially addresses elastic/docs-content-internal/issues/487. This issue is about consolidating LLM connector guides into one place. We currently have in-depth guides in the security docs that other solution docs link to that describe how to set up the LLM connectors. We think this content should instead be in the Kibana connectors reference. Currently the LLM connector pages in that section are basically stubs — they don't give much useful detail about how to complete setup.
We plan to remove these guides from the security docs and add them to the connectors reference. This will require changes to the kibana repo to add the content, as well as changes to the docs-content repo to remove the content and add links to the content's new home. This PR addresses removing content from the docs-content repo, adding redirects, and updating links.
DO NOT MERGE THIS UNTIL WE ADD THE CONTENT TO ITS NEW HOME!