You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One idea I've had when creating slides with Markdown is to allow to put the Markdown text into a separate file. The impress html presentation would reference the file and its contents would be added as text content for the element. Something like:
This would enable a use case where you can have an empty impress.js html presentation as a template and engine, and the úser creating the slides just writes the content.md file.
The text was updated successfully, but these errors were encountered:
Maybe we can use <script type="text/template" src="xxx.md"> to include external file without introducing new attribute?
Currently, we can use <script type="text/template"> to embed markdown contents. The advantage of using <script> is that we don't need to escape </>/&...
<divclass="slide markdown"><scripttype="text/template">Wecanusehtmltaglike`<pre>`directly,don't need to escape it.
</script></div>
I generally like the suggestion to reuse existing tag... even if overloading existing HTML tags feels a bit "potentially dangerous".
I'm not sure I follow your thinking about escaping <, >, &... It seems to me rather a disadvantage that such content would behave differently compared to the same content inside a <div class="step" ...>
Also, note that Markdown content can create multiple slides using ----- separator. But in your suggestion the markdown content is inside a div that is a step. It would be unintuitive that an element inside the div can create more div's at the parent level.
In short, I seem to prefer that we introduce a new attribute to the step div.
One idea I've had when creating slides with Markdown is to allow to put the Markdown text into a separate file. The impress html presentation would reference the file and its contents would be added as text content for the element. Something like:
This would enable a use case where you can have an empty impress.js html presentation as a template and engine, and the úser creating the slides just writes the content.md file.
The text was updated successfully, but these errors were encountered: