-
-
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 enter, exit terms #25
Conversation
Closes GH-24.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this terminology we want to include in this repo?
Or is this something that should be linked to an external resource?
If the terminology is kept here, should it also be added to mdast
, hast
, and nlcst
? Maybe remark
, rehype
, and retext
?
Thanks for checking in! Yes, I’m going with your last paragraph. I laid the problem out a bit in the issue: I think that adding more back-and-forth references is good. Although, for the external resource: I can see the glossary becoming rather big, in the future it could be a different project? |
(for these terms, it arose because hast has a concept of “spaces” that are automatically toggled when entering and exiting, such as described here: https://github.com/syntax-tree/hast-util-to-parse5#space and in other places) |
I was thinking the same thing. |
This does align with my goals a) everything is its own module and b) being welcome to other projects! Would this be something like the initial section of the babel plugin handbook? Do you have other resources? |
Exactly like that.
|
There are also tools for creating and organization larger documentation sites. |
A bit random, but we recommend docusaurus 😉 The next major version (still wip) https://v2.docusaurus.io/ is powered by MDX (part of unifiedjs) |
Moving this discussion to syntax-tree/ideas#7 |
Closes GH-24.