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
Right now you can define a CSS style as a global directive to extend a base theme.
It appears this can only be written inline, e.g. from documentation:
If there is a considerable amount of styling being applied, it would be useful to be able define a local CSS style file and simply set its path in the style directive, e.g.:
---theme: base-themestyle: "style.css"---
style.css file would then contain
section {
background-color:#ccc;
}
The text was updated successfully, but these errors were encountered:
Nice suggestion, but Marpit cannot handle local files while rendering.
We have to manipulate style defined in style directive or <style> tag via PostCSS for converting style to suit to Marpit slides. So it requires loading CSS content if it would support external CSS, but the base converter (markdown-it) does not support an async architecture that is desired to handle file I/O.
In addition, it would prevent working on the environment without supporting file system, like a browser and web worker.
I agree with this suggestion, but we need to solve these problems.
Right now you can define a CSS style as a global directive to extend a base theme.
It appears this can only be written inline, e.g. from documentation:
If there is a considerable amount of styling being applied, it would be useful to be able define a local CSS style file and simply set its path in the style directive, e.g.:
style.css
file would then containThe text was updated successfully, but these errors were encountered: