Move plugins to seperate package?

[chrisjsewell]

The core can almost be made v1.0.0 now since it won't change much outside porting new versions of markdown-it.
The plugins though can be more changeable, so should probably be moved to a different package, with a different release cadence

Its a bit of a pain though, for maintenance, if both are in different repositories.
But I've never housed to packages in the same repository before, so don't know if thats a good idea 🤷

[choldgraf]

something like markdown-it-py-extra?

Where do you envision the biggest pain points for maintenance? Are those things we could design automation / documentation / etc around? I have been impressed with the extent to which automating releases has made it relatively easy to have lots of smaller packages rather than one monorepo

[chrisjsewell]

something like markdown-it-py-extra?

yeh or markdown-it-py-plugins

Where do you envision the biggest pain points for maintenance?

Let's just say its added hassle than I can be bothered with right now lol.
Nothing major TBH; you'd still want all the documentation centralised here, so (a minor thing) you couldn't use sphinx autodoc, maybe some other little things

[choldgraf]

quick thought: I think one benefit of those plugins being separate is that they could be used as examples for how others could extend markdown-it-py w/ their own packages if they wished.

[chrisjsewell]

Oh yeh well they serve as that now, i.e. all folders in https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/extensions are self-contained plugins

[choldgraf]

yeah - I was just thinking if they were standalone packages then they could be almost like cookiecutters - just copy the package, swap out the bits for your custom extension, and publish on your own

[chrisjsewell]

Oh they're not each being separate packages though. That would be madness lol; they're only a few 100 lines of code max