Client for the Serrano and Avocado stack
Cilantro provides various modules and utilies which act as sane defaults for interfacing with the Serrano API. "Out of the box", Cilantro provides a default interface which is suitable for most use cases or it may be used strictly as a standalone client-side library in which specific modules are used to create a custom interface.
Since this is a client for supporting data discovery applications, the UI must be flexible in order to support different workflows that are employed by the kind of data the application is representing.
Cilantro relies on a Serrano-compatible API with version 2.0.15+
npm install cilantro
bower install cilantro
Fork the repository, clone it locally and create a branch for the issue/feature you are developing.
If doing Sass development for the default client, the following are required to compile the SCSS files:
If doing CoffeeScript development, the following dependencies are required to compile CoffeeScript files and run the optimizer:
Yes, makefiles are still cool.. here are few targets to get you going
watch- Starts a Node and Ruby process in the background to watch CoffeeScript and Sass/SCSS files
unwatch- Kills the Node and Ruby processes
sass- One-time SCSS compilation
coffee- One-time CoffeeScript compilation
optimizefor a pre-distribution build
client- Performs build and optimize setup and collects all static assets into the client directory
all- Performs a
watchfor continuing local development