-
Notifications
You must be signed in to change notification settings - Fork 25
Use relative paths to import other markdown files #350
Copy link
Copy link
Closed
Labels
effort: lowEasy or tiny task that takes less than a day.Easy or tiny task that takes less than a day.priority: 1This is important. It should be dealt with shortly.This is important. It should be dealt with shortly.type: refactorChange that neither fixes a bug nor adds a feature.Change that neither fixes a bug nor adds a feature.work: clearSense-categorize-respond. The relationship between cause and effect is clear.Sense-categorize-respond. The relationship between cause and effect is clear.
Description
Using relative paths to import other markdown files make it easy to generate LLM-ready markdown files. The objective is to embed the content from imported files into the parent file. For example,
import AdmonitionSimpleCode from "../../../snippets/_admonition-simple-code.mdx";
<AdmonitionSimpleCode />would be translated into
:::caution
The code in this guide is not production-ready, and is implemented in a simplistic manner for the purpose of learning.
:::The LLM text plugins work well with relative imports.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
effort: lowEasy or tiny task that takes less than a day.Easy or tiny task that takes less than a day.priority: 1This is important. It should be dealt with shortly.This is important. It should be dealt with shortly.type: refactorChange that neither fixes a bug nor adds a feature.Change that neither fixes a bug nor adds a feature.work: clearSense-categorize-respond. The relationship between cause and effect is clear.Sense-categorize-respond. The relationship between cause and effect is clear.