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

External plugins guidance and ecosystem #319

Open
nixjdm opened this issue Sep 21, 2022 · 1 comment
Open

External plugins guidance and ecosystem #319

nixjdm opened this issue Sep 21, 2022 · 1 comment
Milestone

Comments

@nixjdm
Copy link

nixjdm commented Sep 21, 2022

Mistune users are able to write there own plugins, and when they do this locally, it is easy enough for them to import and use there plugin code, so it's available when they use Mistune. Is there a preferred way or best practice for how users should publish their plugin? What is the best way one could find community-made plugins? If there are such things, I propose adding them to the docs.

Taking some inspiration from Lektor, projects could be published to pypi with a mistune- prefix so they are discoverable via pypi's search bar, or you could maintain a docs page linking to them. Perhaps PyPA would allow a new trove classifier to list Mistune as a framework, as well (makes sense to me).

I thought of this coming from the idea that Lektor could more easily pull in arbitrary Mistune plugins. lektor/lektor#1076

@nixjdm nixjdm changed the title External plugins External plugins guidance and ecosystem Sep 21, 2022
@lepture
Copy link
Owner

lepture commented Sep 25, 2022

I've added a community file for mistune v3 plugins: https://github.com/lepture/mistune/blob/v3/docs/community.rst

Developers can send PRs to add their plugins here.

@lepture lepture added this to the Version 3 milestone Nov 25, 2022
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

2 participants