✨ feat: allow relative paths for image shortcodes #222
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.
Summary
This PR updates all image shortcodes to support relative paths.
Changes
All image shortcodes within the theme have been modified to first attempt to locate images using a relative path. If the image is not found, the shortcode then defaults to the specified absolute path.
Before, for co-located assets, this was necessary (e.g. for a post in blog/shortcodes/index.md):
Now, it's possible to use the same format of relative path that you'd use for a normal image:
Accessibility
No specific accessibility changes were made in this PR, as the updates primarily concern backend image path handling. The front-end display and accessibility of images remain unchanged.
Type of change
Checklist