I get around this simply by
> ā Note to self
> If apply the Suchman's ideas to Agile and Waterfall, it's more like do we use planning models.
>
> If we use planning model, then responding to change, means plans
It will show up as
Which is good enough for me
Any news on that?
Good idea!!!
Thumbs up for a plugin like this!
I would also love to see an Admonition plugin coming to life 
!
Here are other examples, in case one of the experts have to time to take a look at this 
:
Somehow, I thought this could be achievable solely from CSS, like the Kanban boards in the wonderful Spectrum community theme 
ā¦ But, as my CSS is really rusty, I probably wonāt be able to help there 
.
Decided to take a stab at this. Check it out here:
The admonitions are basically a direct copy of the ones from the Material for MkDocs above, but I show the css to modify them if you want to customize the look.
I just wrote this plugin and didnāt do too much testing, so I wouldnāt be surprised if it could be buggy, but it is a pretty simple one so hopefully it works well.
Edit: I also havenāt submitted it to the community list yet - you have to manually download it from the Releases section on the repository.
Yeah, it could be achieved through Styling, since that what it boils down to. The user just needs to write HTML Markup instead of Markdown. I actually want to include something like that in the theme!
Hey, thanks. I just released 0.0.5 that allows the admonition to be collapsible.
Iāll probably submit it to the community plugin list soon!
Sounds awesome!
What kind of versioning do you use?
Once itās submitted as a community plugin, Iāll go to 1.0.0 and then use typical semantic versioning from there, but honestly sometimes I donāt follow it well (like this release should have been a minor version update).
I am still using 0.0.4 until it is available on the Community Plugins, but I just noticed this. Could this be fixed somehow? The breaks donāt work. I know that it is because it gets turned into a <p> tag. So either each line has a new <p> tag, add <br /> or leave it as <pre> ? Just some suggestions.
<p> tag.content: flags if title: or collapse: is usedThis should fix that issue. The content should render exactly like regular markdown outside of code blocks.
The only thing I could find that gives the admonition block fits is nested code ā if its the last thing in the block it will render fine (and even do the prism highlighting), but if thereās content after it, that content will be placed outside the block.
Please also regard the Pandoc fenced divs and pandoc-latex-admonition a possibility.
I have been using these with Pandoc and LaTeX in times before Obsidian ā¦
Hi there! Your plugin is a great shot, yet Iām struggling with customizing default titles for each text block. For example, Iād like not to rename āNoteā every time with the ācontent:ā row but to give it another default title. Any suggestions?
In version 0.2.0 I removed the requirement to have the content: parameter if you have a unique title, which helps.
Right now, there isnāt the ability to do custom default titles, but I was planning on adding it. This is a little tricky because the plugin is telling Obsidian to treat each admonition type as a code block language (like javascript or mermaid), so it could collide with other languages and exhibit weird behavior.
The plugin is now part of the community list, so if you have it installed, please re-install it from there.
Thanks!
A really great plugin! Changeable titles possibly with customizable images would make it perfect.
Thanks for this!