-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing for reusable content through includes #227
Comments
Both of Marpit and Marp Core are designed to work in anywhere, not only the local file system but also web app (Marp Web). So we cannot add the feature depending on local file system as our framework / core. But you can extend the syntax via markdown-it plugins if you want. markdown-it-include may be helpful in this case. |
Hi @yhatt. |
No, Marp for VS Code does not allow any plugins for users safety. You can use features only defined in Marp Core. |
Thank you so much @yhatt. What do you think about a solution based on JavaScript? It would be something similar to use mermaid inside markdown only, which works in VSCode. |
I tried the follow code, but did not work.
|
That is feasible given the principle of Markdown's transparency for HTML element If you still want that, an inline script should wrap with HTML comment |
Many thanks @yhatt. It worked for me. For the ones that looking for a solution I can share the code bellow:
|
Can this feature work in vs code plugin now? |
@calidion Accept the situation and use Marp CLI. The reason why Marp/markdown-it plugins cannot be used in the VS Code extension is explained in marp-team/marp#543. |
I wasn't sure whether this was a marpit or marp-core question, apologies if I got this wrong.
Is there any plan for an include directive that will allow me to have a separate file which will be imported at render-time?
For example:
This will permit me to use boilerplate text on all slidedecks, and make it much easier if information contained within the text changes, but also for things like church presentations where song words would need to be included in subsequent slidedecks.
The text was updated successfully, but these errors were encountered: