A minimal static site generator inspired by Middleman and Sprockets, compatible with some gulp plugins. The project is currently very experimental, use it for fun. Things will change.
This project is an attempt to port a subset of middleman to the node.js ecosystem.
We are specifically targeting the features that are useful when building single page JS apps.
If you already love middleman and Sprockets but want/need to use node.js, this might be interesting to you.
The name "Orangejuice" because of gulp and you know, it's healthy and tasty.
- Powered by node streams & compatible with many gulp plugins
- Sprockets-like "include" directive for file concatenation
- Use Gulp plugins as Sprockets-like file processors
- Built in http server (rebuilds files on browser refresh, no flaky fs watch).
- Out of the box support for: less and ejs
How is it different from Gulp, Grunt, X?
Orangejuice favors convention over configuration. For example, Grunt & Gulp provides powerful API's for building very customized build scripts. This requires you to write a bit of code everytime you want your build system to do something new. Each step in the build pipeline is carefully orchestrated so every project becomes special. This means there's a lot of copy-pasta going on when starting something new.
Orangejuice is inspired by Sprockets and uses a convention approach: A set of simple rules are used to determine what files to build, how to build them and where to put them. Files are processed bases on their filename extensions.
Example: "index.html.ejs" will be run through the EJS processor. These processors are gulp plugins, which allows us to leverage a large collection of great existing plugins. If you want to teach Orangejuice something new, you just have to define the mapping between a file ending and a gulp plugin. That's it!
npm install orangejuice
Your project should have a so called "ojfile.js" which is used to configure and run Orangejuice.
Here's a minimal ojfile with comments:
#!/usr/bin/env nodevar oj = ;// The directory with your source tree, relative to the ojfile.ojsourcePath = 'source';// The directory you want to build to, relative to the ojfile.ojbuildPath = 'build';
Here's another ojfile that uses a gulp plugin to compile html files into the angular template cache. In this case the The files are named .html.ngt so we register the processor for the 'ngt' file ending.
#!/usr/bin/env nodevar oj = ;var html2js = ;ojsourcePath = 'source';ojbuildPath = 'build';oj;
Make your ojfile.js executable:
chmod +x ojfile.js
Build once and quit: ./ojfile.js build Start the server: ./ojfile.js Start the server on a custom port: ./ojfile.js server -p 1111
What about examples?
We've made an Angular.js template project that builds with Orangejuice.
It's the best reference to how Orangejuice works right now:
Run the bats e2e tests:
Licensed under the MIT license.