-
Notifications
You must be signed in to change notification settings - Fork 19
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
add support for custom section attributes #17
Comments
Love this feature Especially the idea of markdown Can I help? I've read through the config.xml and mindslide.xsl but my xslt is rusty. A little help with design, or functional requirements, might help me create a patch :) |
Hi @melvincarvalho, Reveal.js (the engine behind mindslide) already supports markdown and the likes: Such a feature would therefore require to
Let me know if this speaks to you at all... or if you have other ideas or want more help. |
Markdown is just one of the many features of Reveal that applies to a section (i.e. slide). So, if on your way to markdown, you figure a more generic way to support multiple features that would be even more interesting. look in https://github.com/hakimel/reveal.js for, among others: data-transition, data-autoslide, data-background_, fragments ,... One of the first question being always: how can the user input this info in a user-friendly way in Freeplane? Thanks again ! |
Great, thanks for the very clear explanation. Indeed a generic solution would be cool. For markdown, I see two ways
There may be other approaches. I'll look into more detail! |
I hope it's OK to add this link here, as "food for thought", while we are in design mode https://rajgoel.github.io/reveal.js-demos/anything-demo.html#/4/1 It's on the topic of making slide content more varied. The reveal plugin "anything" offers some nice use cases |
sure is. I would like to keep the mindmaps nicely readable in Fireplane though... and therefore not so sure about more javascript-based content that MM will not be able to display/interpret.... but it's just my view and I'm open to reconsidering. |
including data-markdown, data-autoslide, data-background_, data-transition_; maybe as node attributes?
The text was updated successfully, but these errors were encountered: