[docs] Migrate docs from AsciiDoc to Markdown#1116
Merged
leemthompo merged 2 commits intoelastic:mainfrom Mar 4, 2025
Merged
Conversation
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
Contributor
|
@colleenmcginnis did you want to target the |
Contributor
Author
No. The |
yansavitski
approved these changes
Mar 4, 2025
Contributor
|
FYI I opened link fix PR in logstash repo |
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
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.
Migrate docs from AsciiDoc to Markdown. The preview can be built after #1115 is merged.
Note: Ideally we would also remove the AsciiDoc files from the
mainbranch. In other repos the docs team has been creating a temporary branch,do-not-delete_legacy-docs, to host legacy AsciiDoc content until we can turn on our new Markdown docs when 9.0 launches. However, no one on the docs team has permissions to create a new branch in this repo. Would someone be able to assist us with this?cc @leemthompo @elastic/search-experiences-team (I can't add reviewers)