Skip to content
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

Drop indented #41

Open
rwxrob opened this issue Nov 26, 2022 · 0 comments
Open

Drop indented #41

rwxrob opened this issue Nov 26, 2022 · 0 comments

Comments

@rwxrob
Copy link
Owner

rwxrob commented Nov 26, 2022

It's just the same as fenced and is harder to maintain properly. Better to just fence it all off and give it a syntax class if needed. In fact, fenced is all that is ever really needed. We should allow literally anything after the fence (like Pandoc which turns {note} into a class. This will allow the use of syntaxed fence blocks to be used for divisions as well as actual language classes. This is what Myst allows for "admonitions" even though they should probably be done within footnotes instead.

We won't be specifying what to do with what comes after the initial fence at all. That is entirely up to KEG apps to decide and greatly differs on how they will be rendered. However, we do want to caution about putting to much actual paragraph style text in such things since most Markdown engines just won't render it at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant