Add --resource-path option to seperate images from markdown files #30
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
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.
Currently, the image-path has to be relative to the script location. Unfortunately, this results in some markdown editors (e.g. VSCode) not being able to preview the markdown files correctly (i.e. with images).
Pandoc has an
--resource-pathoption, allowing to specify where to look for resources. This pull request adds--resource-path=.:srcso that the script location and thesrcfolder are searched for images. In addition, the placeholder image was moved to its ownimgdirectory, providing a better separation of contents and - in my opinion - a better bootstrap.