Migrate all user documentation to elastic.co #1765
Merged
Conversation
This file contains 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
sethmlarson
force-pushed
the
document-elastic-transport
branch
from
6964476
to
f063c0c
Compare
szabosteve
approved these changes
Oct 20, 2021
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.
Previously we've had our documentation for constructing, configuring, and integrations for the client spread across Read the Docs and elastic.co/guide. This is a pain to maintain and likely we're either missing or having varying quality of content across the two platforms.
To fix this issue I've migrated all user documentation to elastic.co and plan to use RTD as an API reference, potentially with automatically generated documentation when we begin generating JSON structures and enums.
These docs are specifically for 8.0, 7.x documentation will stay on RTD as-is.