Harp compile
Export your harp site to flat static assets – HTML / CSS / JavaScript.
Why?
With Harp, you don’t need to compile or watch your project at all times—the compile files don’t need to appear alongside your source files, cluttering everything up. Still, there are still times when you might want to compile all your preprocessed files to HTML, CSS, and JavaScript:
Apache Cordova
Building a mobile application just got even easier.
harp compile
exports directly to an Apache Cordova / PhoneGap-friendlywww
folder.No Lock-In
If for whatever reason you fall out of love with Harp, just export your project and deploy it on any stack or cloud provider that serves static assets.
Usage
harp compile [options] [projectPath] [outputPath]
Mobile Example
Try creating a project called mobileapp
by running harp init mobileapp
and then compiling it:
harp init mobileapp
harp compile mobileapp
Running the compile command would generate the assets as follows:
mobileapp/
+- www/
|- index.html
+- main.css
Backup Example
Lets say we have a project called example in our apps folder. We could export it to static assets in our Desktop/backup folder by running the following command.
harp compile ~/apps/example ~/Desktop/backup
Note The backup folder is automatically created and is assumed to be empty.