jekyll/jekyll-import

Documentation on importers is not helpful

ashmaroli opened this issue · 2 comments

The importer-specific page directs the visitor to run a Ruby script instead of using the CLI provided by the plugin.
For example, the documentation for importing a wordpress.com site directs the visitor to run:

$ ruby -r rubygems -e 'require "jekyll-import";
    JekyllImport::Importers::WordpressDotCom.run({
      "source" => "wordpress.xml",
      "no_fetch_images" => false,
      "assets_folder" => "assets"
    })'

instead of

jekyll import wordpressdotcom
parkr commented

There is a lot of cruft in this project that has accumulated over time. I think the reason we went this route originally was because the "jekyll import" subcommand was unreliable (jekyll needs to require jekyll-import for the subcommand to exist). So we went this less optimal route.

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.