Markdown issues

Hi, this is rather a markdown question (I suppose) and it might already have been asked, in such case, sorry. I have a list of pictures (with ) and I can’t apply markdown attributes to the individual figures.

- 	![bonobo diet](/Images/images_article_instincto/bonobo_diet.jpg "Bonobos")
	{.center}
- 	![bwindi mountain gorilla diet](/Images/images_article_instincto/bwindi_mountain_gorilla_diet.jpg "Bwindi Mountain Gorilla")
	{.center}
-	![Ngogo Eastern Chimpanzees diet](/Images/images_article_instincto/ngogo_eastern_chimp_diet.jpg "Ngogo Eastern Chimpanzees")
	{.center}
-	![Rio Muni Central chimpanzees diet](/Images/images_article_instincto/rio_muni_central_chimp_diet.jpg "Rio Muni Central chimpanzees")
	{.center}
-  	![Human diet](/Images/images_article_instincto/human_diet.jpg "Modern humans, USDA, 1992")
	{.center}
{.carousel}

carousel applies to the list, a figure+attribute on their own also works, but not this. The classes won’t apply. Tried two spaces indentation, a tab, nothing… what else ? I’m not going for shortcodes, before someone asks ! It should work.

There are inline images and block images and your use is inline (in a list item). So the block method to apply attributes (in a newline) seems to be ignored. I never needed this, so I have no solution for you, but two tips:

  • did you try the method for list items where every list item is separeted by two newlines (an empty line between each list item?)
  • did you try your luck with standalone-images

A little hacky is probably to give attributes to the list and then format via ul img in your css instead.

1 Like

an empty line ? Never done that, thanks !
But then how would you go about making a new list next to the first ? I found an empty {} attribute list in a new line does the trick, but it seems rather hacky imho.

I am quite OCD about semantic and a list always has an introduction paragraph or headline before (for me). So that issue would not come up. Markdown is a little bit lacking features for more creative text output options, because it basically was born out of documentation formatting requirements.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.