I’m adding indirect links to md2pptx - because tools like iThoughts seem to generate them.
These are of the form:
[IBM Website][toIBM]
[toIBM]: https://www.ibm.com
As opposed to:
[IBM Website](https://www.ibm.com)
I believe the latter type of link is called an inline link.
Anyhow, I’m wondering what he advantages are for one over the other - and would probably allude to the trade offs between them in the enhanced documentation for md2pptx.
Also, I’m thinking I could harvest the links to make an optional “external links” slide - at the end of the presentation md2pptx generates. I wonder what people think of that idea.
But mostly I’m interested in indirect versus inline link usefulness.
Gives you a single list of all URLS used, assuming you use it consistently and exclusively.
For what it is worth, it is a standard Markdown option for links, so if you want your tool to be Markdown compatible, then it should technically support their use.
I’d also add that it would make the Markdown document easier to read and work with. ibm.com isn’t a long URL but that’s rarely the case for me so this could be pretty cool to implement.
Thanks. My stance - which might be a little defeatist - is “make everything my tool can use be valid Markdown”. This is not quite the same thing. But I’m converging on Markdown.
The other thing - which is partly why I asked about it - is improve the utility of expression.
Thanks. Anything to make it easier to write presentations (that could equally become drafts or documents).
It’s actually quite easy to implement.
I’m wondering about whether harvesting links and optionally doing something else with them would be useful. first idea is to allow an optional “external links” slide to be created. (I already do footnotes and Taskpaper tasks as slides at the back of the presentation so this is in that spirit.) In general I’m winning when I use md2pptx over making Powerpoint presentations by hand - so this would put me even further ahead.
Reminding myself that Inline Links tend to be called “Reference Links”. I should probably use that term in the docs to describe the pre-existing support.