Reimplement "single- macro plugins" as pluglets? Contribute to effort to list them? #196
Pinned
fralau
started this conversation in
Community announcement/discussion
Replies: 3 comments
-
Food for thought: discussion #177 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I created a list on a Github wiki page. You are welcome to submit new pluglets. |
Beta Was this translation helpful? Give feedback.
0 replies
-
See also follow-up discussion #212 (what happens if we import code of an Mkdocs plugin into an Mkdocs-Macros module)? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
One of the key purposes of pluglets is to make it easy to replace single-macro plugins (e.g. read_csv) with an equivalent for Mkdocs-Macros.
There are two reasons for that:
The problem: Those plugins are incompatible with Mkdocs-Macros, because they use the same concept and the same syntax -- basically they exist just to implement a macro. But users need that functionality so they are taken in a catch-22. If we want Mkdocs-Macro to win, we need to re-implement those functions.
The saving grace: Re-writing those plugins as pluglets is easier and more elegant. That is because there is no need to reinvent the wheel with the mechanism for macros; it is already there.
What do you think of that? Should there be a community effort in that direction?
Beta Was this translation helpful? Give feedback.
All reactions