...And add a task that will rename the .sample to the .json if there is no happy-plan.json.
This will make update to end project using merge simpler (avoiding conflict if the user update the happy-plan.json for his need).
Easy to do. I can take care of that.
What do you think ?

In package.json :

"scripts": {
        "start": "node app/server.js",
        "test": "grunt qunit",
        "build": "grunt build"
    }

It allows you to do for instance npm start

poke @MoOx

As we now have the possibility to create themes and install them via bower, we should find a name convention for themes.

What do you think about hpt-:name or happytheme-:name? I prefer the first one.

TODO: https://github.com/tschaub/grunt-gh-pages

I don't understand the behaviour of how we use .bowerrc.

I was wondering why .bowerrc isn't versioning and I saw that it's generated by Happy Plan.

So I ran the grunt cmd and I saw that compass couldn't import normalize.scss, which is totally normal because I couldn't install normalize.scss via bower coz I don't have any .bowerrc file.

Why .bowerrc is generated by happy plan? How do you do when you didn't run one time grunt and you need to install something via bower?

• https://github.com/marijnh/heckle
• https://github.com/assemble/assemble
• https://github.com/shama/grunt-docs
• https://github.com/clavery/grunt-generator

@MoOx We cannot run the default task if there's no svg file because of webfont.

Log with Github on Travis-CI & activate this repo :)

• 1: http://thenounproject.com/noun/person/?dwn=&dwn_icon=#icon-No4895
• 2: http://thenounproject.com/noun/boy/#icon-No5190
• 3: http://thenounproject.com/noun/excited/#icon-No14706
• 4: http://thenounproject.com/noun/happiness/#icon-No12481
• 5: http://thenounproject.com/noun/happiness/#icon-No12480
• 6: http://thenounproject.com/noun/happiness/#icon-No12476
• 7: http://thenounproject.com/noun/happy/#icon-No3060
• 8: http://thenounproject.com/noun/happy/#icon-No14703
• 9: http://thenounproject.com/noun/happy/#icon-No11332
• 10: http://thenounproject.com/noun/happy/#icon-No2550
• 11: http://thenounproject.com/noun/squint/#icon-No14708
• 12: http://thenounproject.com/noun/squint/#icon-No14705

For the moment, we simply use *.js to compile them into script.js at the end.

The problem is if you have:

• a.js
• b.js
• c.js

and you absolutly need that a.js is the latest script in script.js, you can't.

How to resolve this problem?

poke @MoOx

Since I've refacto all the happy-plan.json, we now don't use absolute path anymore.

Should we? poke @MoOx

In testing, Jekyll plugins seem to be left out of the happy-plan.default.json

Will try to add myself but reporting as issue here too.

What do you think of moving src/_assets/img/svg into something like src/_assets/fontcustom/ or _assets/svg-for-fonts, to avoid the clean:svg task ?

@MoOx you defined:

"dist": {
    "path": "dist/",
    "assets": {
      "path": "<%= happyPlan.dist.path %>assets/",
      "scripts": "<%= happyPlan.dist.assets.path %>js",
      "styles": "<%= happyPlan.dist.assets.path %>css",
      "images": "<%= happyPlan.dist.assets.path %>img",
      "fonts": "<%= happyPlan.dist.assets.path %>fonts",
      "static": "<%= happyPlan.dist.assets.path %>"
    },
    "medias": "<%= happyPlan.dist.path %>medias",
    "root": "<%= happyPlan.dist.path %>"
  },
  "baseUrl": ".",
  "baseUrls": {
    "_": "<%= happyPlan.baseUrl %>/",
    "scripts": "<%= happyPlan.baseUrl %>/js",
    "styles": "<%= happyPlan.baseUrl %>/css",
    "images": "<%= happyPlan.baseUrl %>/img",
    "fonts": "<%= happyPlan.baseUrl %>/fonts",
    "medias": "<%= happyPlan.baseUrl %>/medias"
  },

and you use in jekyll:

base_urls: 
  scripts: "{{ happyPlan.baseUrls.scripts }}"
  styles: "{{ happyPlan.baseUrls.styles }}"
  images: "{{ happyPlan.baseUrls.images }}"
  fonts: "{{ happyPlan.baseUrls.fonts }}"
assets:
  main:
    style: "{{ happyPlan.assets.main.style }}"
    script: "{{ happyPlan.assets.main.script }}"

which means all files go to ./assets/ but you call them without /assets/, whaaaaaat?

Imagine you clone happy plan, you make it work, and we do an update on happy plan, the project where we worked with happy plan must be updated easily without overwriting everything.

What do you think about bringing Zurb Foundation for quick CSS developement ?
Can be add with Bower.

Since media is already plural ;)

@MoOx ? No livereload anymore in the layout?

Using https://github.com/visionmedia/mdconf#mdconf

I'm stuck with static folder. (cc @MoOx)

I need to put some files like CNAME or favicon.png at the root of the website.

The thing is we've got static folder in assets. It's for files which have no compilation, it's just a way to copy paste files there to dist asset folder (/dist/assets/).

Though, these files should be at the root of dist.

There're multiple ways to fix it:

• We stop to use dist/assets folder in dist and we put everything at the root (/dist).
• We use two static folders. One for assets, one for root.

We must think about theme possibility.

I was think about having a theme folder, this is where you download it (via bower?) and you can do happyplan theme:copy --:name-of-the-theme

Why not use for default task the watch task ? (the most used task by hand)

Regarde should watch . and not only *. We don't want to watch folders. Could be create some bugs.

https://github.com/outaTiME/grunt-replace

It could be great to use grunt-replace to change the path of the css/js in the default.html layout.

This will include a help task, so happyplan help will output just "private" commands (not every grunt tasks available).

$ bin/publish.sh
$ node bin/newpost.js

should be

grunt:publish
grunt:newpost (--draft)

Build is actually broken if you have latest jekyll & grunt-jekyll version.
I'm on it.

And use that

https://github.com/geddski/grunt-release

Discovered happy-plan today, looks perfect to me since I use everything provided.

Now, I got everything worked except the scripts.

• I have placed my scripts in _scripts (multiple files)
• I have installed some bower components in _bower components

If I run "grunt" I get a concatted scripts file with the scripts in _scripts. However, I feel l am missing some efficiency trcik here.

How am I supposed to work with this? Do I manually copy the js files from _bower_components to _scripts or do I reference them? How do I change the concat order (jquery etc. must be first)?

https://github.com/nDmitry/grunt-autoprefixer

Maybe there're good ideas there.

• https://github.com/tommy351/hexo
• https://github.com/robwierzbowski/generator-jekyllrb

POST-IT https://github.com/Snugug/static

In financial accounting, assets are economic resources

What do you think of moving src/_assets/content(/img) into something like src/uploads/ ?

If you don't know it yet, http://prose.io/ is a nice online markdown editor that allow you to edit directly .md file of a github repo, with some helpers.

How do we use require for compass?

For the moment, I've added myself this line in compass grunt task:

require: ['animate', 'animation']

This can be nice right ?
Can be done using https://github.com/gruntjs/grunt-contrib-compress

Now that themes are possible, shouldn't we move bower.json into src folder in order to be overwritten easily by the theme?

• Replace all compilated folders from "folder" to "_folder"
• All the "src" is copied excepted "_folder"
• If you need to add something in assets or ./, just add it as you want. If you want to ignore something, just add _ behind the name

What do you think about moving all paths variables into a happyPlan.path part ? Because since I'm adding more config into the happy-plan.json (#10), it will be easier to read...
What do you think ?

See comments here http://stackoverflow.com/questions/5570531/difference-of-purpose-of-build-and-dist-directories-when-doing-a-deploy
dist seems to be more appropriate ?

Add in connect settings:

hostname: ''

@MoOx How do you differentiate components for js and components for css?

For instance, I can have bootstrap.js and bootstrap.css. We need to suggest an arborescence for scss which are yours and scss which are from a plugin.

lftp doesn't do something like rsync. Since build change mtime, we need another tool, which can avoid all reupload...
https://code.google.com/p/curlftpfs/ ?

form MoOx/moox#24

Just to be sure you have nice formated Gruntfile.js & you main script clean :)

EDIT: new issue title is clear now :)

Like we can see with issues #2 and #3, I think _assets not really useless & bring too many weird behavior in the gruntfile (copy but clean & image optimize).
With grunt-contrib-imagemin, images are copied & optimized.
Why not just use an _img folder (for design) & an uploads folder for content related image, video, & content stuffs (or _content_assets ?).
Or maybe just use _assets for content stuffs ? (but make less sense...)

I wanted to check out the themes functionaliy but it's a bit unclear, the docs on github homepage refer to a "happy" command now so I went on to install the binary in the repo (bin/happy)

• Should add to docs how to install the happy bin
• Should make happy installable via brew?

If i move the bin to my /usr/local/bin I have problems

wolfr3:happy-plan noone$ cp bin/happy /usr/local/bin/
wolfr3:happy-plan noone$ happy
-bash: /usr/local/bin/happy: Permission denied
wolfr3:happy-plan noone$ chmod +x /usr/local/bin/happy 
wolfr3:happy-plan noone$ happy

module.js:340
    throw err;
          ^
Error: Cannot find module 'celeri'
    at Function.Module._resolveFilename (module.js:338:15)
    (...)

is this about https://github.com/crcn/celeri ?