You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you move a source file or folder, you must also update all inbound and outbound links to reflect the new file location. `docs-builder` provides tooling to handle this step for you.
4
+
5
+
## `docs-builder mv`
6
+
7
+
Move a file or folder from one location to another and update all links in the documentation. For example:
Copy file name to clipboardExpand all lines: docs/migration/guide/automated.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Migrate Automated Content to V3
1
+
# Migrate automated docs
2
2
3
3
If you have automated documentation in Asciidoc (or any other format) that you need to migrate to Elastic docs V3, this guide walks you through the essentials. Elastic docs V3 (powered by `docs-builder`) allows engineering teams to keep code and reference docs closely integrated for easier updates and greater accuracy.
4
4
@@ -15,8 +15,8 @@ Once you have these files, follow the [Contribute Locally guide](../../contribut
15
15
16
16
Elastic docs V3 fully supports [CommonMark](https://commonmark.org/) Markdown syntax. In addition, we support:
17
17
18
-
* Custom directives — our main extension point over markdown (learn more [here](../../syntax/md-extensions.md#directives))
19
-
* A few GitHub flavored markdown extensions (see the list [here](../../syntax/md-extensions.md#github-flavored-markdown))
18
+
* Custom directives — our main extension point over markdown (learn more [here](../../syntax/index.md))
19
+
* A few GitHub flavored markdown extensions (see the list [here](../../syntax/index.md))
20
20
21
21
In most cases, plain Markdown covers basic needs, and directives add extra functionality as needed.
22
22
@@ -43,4 +43,4 @@ For more information, see [Navigation](../../configure/content-set/navigation.md
43
43
44
44
## Next steps
45
45
46
-
That’s all you need to get started migrating automated docs to V3. As you add more pages or custom features, refer to the linked resources for details on configuring your docset, refining navigation, and leveraging the full power of V3 directives.
46
+
That’s all you need to get started migrating automated docs to V3. As you add more pages or custom features, refer to the linked resources for details on configuring your docset, refining navigation, and leveraging the full power of V3 directives.
0 commit comments