-
Notifications
You must be signed in to change notification settings - Fork 99
Home
jrburke edited this page Jan 25, 2013
·
10 revisions
volo motivation, design:
- Design goals - the top level goals that motivate the design of volo.
- Prior art - discussion of how volo fits in with things like npm, cpm, bpm.
- volo and grunt - comparing volo and grunt.
Best practices for end users:
- Library best practices - the best practices to use when constructing a library that will be used by others.
- Application best practices - the best practices to use when building an application/top level project that uses libraries that also use best practices.
-
add dependency rules - the rules
volo add
uses to find and add new dependencies to a project. The best practices result from the conventions used byvolo add
.
Directories:
-
create templates - template projects that are known to work with
volo create
.
Some docs related to code:
- Creating a volofile - a short introduction to making a simple volofile.
- Creating a volo command - how to create a command that can be run by volo. This is useful when wanting to extend volo itself to do other things, or implementing more sophisticated logic that can be reused by many volofiles.
- Teaching volo add about a non-standard library - teach volo about a non-standard library so it can be easily installed by other volo users