We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when I insert images in posts via markdown they are not responsible and cross the boarders of the post's text.
You can see an example here. The first img in the text is inserted using markdown. The other images are inserted via html.
https://www.cloudcoffeebreak.de/2024/04/06/azure-policies-waechter-der-cloud-compliance.html
In html I can see that there is no class defined for the image inserted via Markdown.
When I add the images via html like this <img class="container"... > they are responsible.
you can find the repo here: https://github.com/chris4jahn/Cloud-Coffeebreak
How can I ensure that all images are responsible even when inserting via markdown?
Thanks for your help.
The text was updated successfully, but these errors were encountered:
Sorry, this is not the version I'm using. I'm using the Jekyll version.
Sorry, something went wrong.
No branches or pull requests
when I insert images in posts via markdown they are not responsible and cross the boarders of the post's text.
You can see an example here. The first img in the text is inserted using markdown. The other images are inserted via html.
https://www.cloudcoffeebreak.de/2024/04/06/azure-policies-waechter-der-cloud-compliance.html
In html I can see that there is no class defined for the image inserted via Markdown.
When I add the images via html like this <img class="container"... > they are responsible.
you can find the repo here:
https://github.com/chris4jahn/Cloud-Coffeebreak
How can I ensure that all images are responsible even when inserting via markdown?
Thanks for your help.
The text was updated successfully, but these errors were encountered: