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
{{ message }}
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
Now that our Markdown directives capability is sophisticated enough, we should be able to create *.mdd.ts (Markdown directive modules, or "MDD"s) which would auto-register directives and web components they wrap.
This would allow, for example, content/github.mdd.ts to auto-register a GitHub directive which would allow usage like :github[org/repo]{latest} to insert the latest release tag of GitHub org/repo into the current text stream. It would be good to allow these directives to be run at both server and client if desired.
MDDs should wrap web components whenever possible so that HTML and Markdown are both first-class citizens.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now that our Markdown directives capability is sophisticated enough, we should be able to create
*.mdd.ts
(Markdown directive modules, or "MDD"s) which would auto-register directives and web components they wrap.This would allow, for example,
content/github.mdd.ts
to auto-register a GitHub directive which would allow usage like:github[org/repo]{latest}
to insert the latest release tag of GitHub org/repo into the current text stream. It would be good to allow these directives to be run at both server and client if desired.MDDs should wrap web components whenever possible so that HTML and Markdown are both first-class citizens.
The text was updated successfully, but these errors were encountered: