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

Standard Importer Architecture #63

balupton opened this issue Oct 4, 2011 · 3 comments


None yet
2 participants
Copy link

commented Oct 4, 2011

As a Developer, I want a standard architecture for importers, so that I can write custom importers easily

Importers should inherit from a standard architecture.

This standard architecture will provide two access points:

  • Via the command line
  • Via the web interface - see #62

Location shall be docpad/lib/


This comment has been minimized.

Copy link

commented Oct 4, 2011

Be aware of importer dependencies.
Wordpress importer depends require mysql lib, datejs, ..
So, why should we add importer dependencies in docpad package.json ?


This comment has been minimized.

Copy link
Member Author

commented Apr 19, 2012

We could knock off importers as plugins in version 5, as plugins can specify their dependencies via package.json for their node ones, or their readme for others.

The difficulty here will be to come up with the events importers need, and a standard architecture for them - this is the hard part.

I would love to have a meeting with your @obazoud as well as other docpad contributors to figure out the best way forward for this - as importers are incredibly important.


This comment has been minimized.

Copy link
Member Author

commented Mar 6, 2013

The ability to extend the command line interface has been added in v6.24.0. This is issue is now closed :) 🍰

@balupton balupton closed this Mar 6, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.