Abstract out Configuration Parsing

[balupton]

We could probably abstract out our configuration parsing.

---

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

[przemoli]

Yes!

Split config into multiple files.

Having helper functions for eco alongside of build config seam strange..

Simpliest thing to do would be to keep current syntax but with import keyword allowing to include content of any "valid" configuration file.

That way developer can keep their specific configs in separate files.

[balupton]

@przemoli thanks! btw, you can require and merge multiple configuration files now already by using docpad.coffee as your configuration file then someData = require('some-data.coffee') to include data from another configuration file. Example here and here

[Zearin]

👍

(Also, thanks for the tip, @balupton ! Gonna start using that right away!)

[Zearin]

Was looking over the source of lib/docpad.coffee.

Holy hell, that is one monstrously long god-class!!!

A huge part of it is config-related. Definitely worth marking this as a priority item.