Damith C. Rajapakse

Introducing an easy syntax that says 'stack horizontally when there is space, overflow to next line if no space' seems like a more user-friendly solution, for both authors and readers....

> Hi @tlylt, @lhw-1 and I were discussing and we think a plugin would work best. It can be a natural extension to our current `codeWrapBlockButton` and `codeCopyBlockButton` Should we...

> In that case, would it be very similiar to the bootstrap grid system? Possibly a simpler version of it (less flexible, but easier to use).

Thanks for looking into this @yucheng11122017 @kaixin-hc 'link with highlight' didn't exist when I posted this, but even now, that feature is not good when you want to highlight a...

Oh? I never used it because I didn't know about it. I don't mind keeping it as it can be useful for printer-friendly versions of a page. Also, the page...

> * Since this is a `markdown-it` plugin, HTML headings will not be included in the TOC as they will not be parsed as Markdown. I see. Should be fine...

A follow up: It looks like the `[[toc]]` in its current form does not work correctly with `include`. i.e., If I include a file that contains a `[[toc]]`, the output...

> I suppose it works with dynamic include? It should work for boilerplate includes because the behavior matches boilerplates (i.e., copy content and then render).

> Boilerplate includes can be static or dynamic right? No such differentiation as far as the current documentation goes. 1. Default: render content in original location and then copy over...

`copy over content and then render based on the new location` vs `render content based on the included location and then copy over to includer` From the user's PoV, is...