-
Notifications
You must be signed in to change notification settings - Fork 101
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 fragmented slides. #36
Comments
Can you please give more details? |
maybe not ideal, but if you're using markdown you can input the html directly
|
Please propose a markdown syntax for:
|
ping. we still need an idea for the syntax. |
Could we do something similar to what I am thinking about something like this:
|
The issue seems to be, "how do we add html attribute syntax to markdown?" While I think it's probably as easy to just write the html (same issue with all other approaches of adding attributes that I've seen), I think @kimsk 's idea to continue the syntax of reveal.js would keep the two projects in sync which would probably have more benefits than rolling anything custom unless a really clean syntax is proposed. |
Probably a dumb question, but here goes..., |
You mean building slides? Did you clone the master branch and run the
|
Have you looked at hakimel/reveal.js#677? They included a reference too: https://github.com/VonC/reveal.js/blob/classes_in_markdown/test/test-element-attributes-markdown.html
|
@forki Indeed, from the master branch I can run build.cmd and it opens the browser, but from the master branch I'm not sure how to edit the FsReveal source. I branched off of develop to make code changes. Perhaps that's the source of my error? |
@reidev275 Are you talking about editing FsReveal code (FsReveal.dll)? |
Yes, mapping paragraph literals with the pattern you mentioned into literals with html expected from reveal Sent from my iPhone
|
Ah now I get the issue. You want to test your custom built fsreveal.dll!? There are two simple ways:
|
No description provided.
The text was updated successfully, but these errors were encountered: