http://net.tutsplus.com/tutorials/tools-and-tips/working-with-less-and-the-chrome-devtools/

1. Prevent npm install.
2. Prevent bower install. Maybe we can just fire an update?
3. Don't touch the directory structure, and always ask for overrides or changes on files.

https://github.com/alanshaw/david

I have a project using Nginx for this purpose and I like the idea to remplace it using just a connect middleware.

https://github.com/dendril/nginx

1. Split in several files.
2. Add the installation for humans npm install generator-tamagotchi
3. Guide for contributors?

http://yeoman.io/blog/cleanup.html

In order to prevent fails in versioning process just integrate grunt-release plugin which will handle all the steps we need.

There is another plugin named grunt-bump but I guess the first one add some cool extras (npm publish for example).

Discussion about automatic sprites.

We are now able to define a folder with different images and then run:

grunt montage

The output will be a new folder containing a .png image and .css file containing each class for matching the position in the sprite.

There're some problems. We need to integrate this with the actual work process:

Actual work with bootstrap

The synergy sprite is already created and we have a sprites.less file which contains every class to the icons. We should match exactly that with this plugin and there's no time.

It's a little tricky to refactor this now with no time. Could anybody help me?

What do you think?

What if we have different images sizes? (Actually, we have)

I'm proposing to create different folders with contains just one sprite for all the images matching that size. e.g : every image which size is 16x16 will be contained in a folder called img_small and in that folder a img_smal.png sprite.

We could have three folders, small_img, medium_img, big_images and bigger than that I suppose it won't be on a sprite. (should research about image sizes we are going to use)

The folder approach solves the problem with different images size (three different types of classes: a general one for the background-image, each class defining the background-position and the needed for define each image size) and automates the process easily.

Which is the best way to do it?

Any others thoughts?

This issue is related with https://github.com/dendril/bootstrap/issues/38

As a developer I want to type grunt test and then:

1. Prepare all js files placed in tests folder.
2. Run test using phanthonjs.

Note: Take a look of https://github.com/yeoman/generator-karma

What is SourceMaps?

The idea is be able to debug .less and .min.js files in a human way 😄

The current generator doesn't handle any type of template engine. For now consider the use of Underscore templates.

In dev phase we are using the text plugin for require to load the html as text. When we are in the browser the transformation from text => js is time consuming and doesn't make sense to been doing that in production.

The idea is compile all the template on server side as part of the build process we will run before deploy the application.

There is a plugin for JST approach https://github.com/gruntjs/grunt-contrib-jst take a look at this as a possible approach.

Project reference https://github.com/globant-ui/arialinter

Line 12 should be "require-jst" : "https://github.com/ahutchings/require-jst.git" instead of "require-jst" : "[email protected]:ahutchings/require-jst.git" to fix bower install error

File
app/templates/docs/0000-index.md

Error:
Git integration with TFS: bad link

As a developer I want to type grunt dev and then:

1. Enable livereload on all the compiled assets.
2. Compile less files.
3. Bundle all the js but enable debugging using sourcemaps.

References:

https://npmjs.org/package/grunt-jsbeautifier
https://npmjs.org/package/grunt-prettify