Bundler has first-class support for this kind of thing with groups. Would it make more sense to use groups?

Isn't the Ruby comment on the preceding lines stating exactly why I did not use a Bundler group or is the comment not clear enough..?

I see it now, yes. I have been reviewing on GitHub Mobile which does not show all the context – even less when you're working on a comment. Do you think listing the dev dependencies on RubyGems.org is doing anyone any good? I don't think I have ever looked at dev dependencies before... How would they know which dependencies are for each importer? I feel like folks would actually prefer this all on one page, on our docs site. So should we move these to the Gemfile and just leave it be? Since we're thinking about these things, could we do better documenting dependencies?

In terms of ergonomics, jekyll-import leaves a lot to be desired. The first time you run, you get an error since it's very unlikely you already have all the dependencies. Could we launch bundler and auto-install dependencies somehow? And we even ask users to run the Ruby interpreter and input a Ruby program. We don't even propose users use the CLI...