directory
directory copied to clipboard
Import plugins from documentation
Right now, we list available plugins in the Jekyll documentation.
We should create an entry on the site for each of these plugins.
Can we scrap these?
Scrap or scrape?
We should probably keep them.
We could probably scrape them, but brute force would probably take less time than writing a proper scraper, and it's just a one time import (I hope)
@pathawks Let's make sure we port any additions to the page in jekyll/jekyll over to here so that once you're ready we can replace the list with "Want plugins? Go check over here!"
OK, I'll take the time to port the plugins. Let's get this done!
I realize that some plugins are just ruby gists created 6 years ago, and that they are not necessarily compatible with Jekyll 2 or 3, should I add them anyway?
I realize that some plugins are just ruby gists created 6 years ago, and that they are not necessarily compatible with Jekyll 2 or 3, should I add them anyway?
I don't like the idea of including plugins that are not at least compatible with Jekyll 3.0.
I don't like the idea of including plugins that might be lacking installation instructions.
Maybe ditch it if it's just a Gist. If it is a GitHub repo, maybe @jekyllbot (or one of us) could open an issue in the repository:
Jekyll's plugin registry is moving.
This plugin is currently listed on jekyllrb.com, but we are migrating our listing to a new site.
If this plugin has been confirmed to be compatible with Jekyll 3, please open a PR here to add this plugin to the new registry.
?
β€οΈ It would be great to parse the current plugins directory and generate a PR to the plugin author.
There are more than 200 listed plugins, and we don't know what version they are compatible with. We're not nice with Jekyll users, we just say : here is all the contributions made since 6 years, help yourself π
here is all the contributions made since 6 years, help yourself π
I agree, the current situation is no good.
That's why I think moving plugins to the new directory should require at least a little effort from the plugin author.
No feedback, no plugin listed?
No feedback, no plugin listed?
Right. We send them a notification, and that's it.
If a year from now, an author decides to update a plugin to work with the latest version of Jekyll: cool :+1:
If a plugin has been abandoned, it won't be listed in the new directory.
I have - manually π« - imported 75% of the listed plugins, I'm starting to see the end of thisβ¦ π