Include standard Gruntfile.js

humanmade / hm-base

Standard project layout for Human Made Projects.

81 stars 18 forks source link

Include standard Gruntfile.js #10

Closed danielbachhuber closed 10 years ago

danielbachhuber commented 11 years ago

So that it's easy to Grunt-ify a new project, we should include a standard Gruntfile.js for HM Base.

mattheu commented 11 years ago

For a standard gruntfile to make sense, it needs to know the directory stucture of the theme so I added a sample theme that can be used as a starting point.

Add some folders and JS/CSS files.
Add header.php index.php and footer.php with some basic markup.
Add functions.php which includes conditionally loading minified/dev js/css depending on value of HM_DEV

mattheu commented 11 years ago

Another angle we could approach from is to run grunt from within the theme. We could then use a grunt-init template to get set up similar to 10up. To be honest, I think this might be a better approach.

Downsides:

Navigate to theme dir to run grunt
Cannot easily add files outside of the theme to be concatenated by grunt. (should we be doing this anyway?)

mattheu commented 11 years ago

For my version of the grunt-init template see here...

https://github.com/mattheu/grunt-wp-theme/tree/master

willmot commented 10 years ago

@mattheu does this make sense to merge?

mattheu commented 10 years ago

This makes sense to merge if having grunt in the project root is the way to go. This is how we are using it on several projects now.

Anyone else have any opinions on this? @joehoyle or @pdewouters maybe?

It also doesn't prevent an individual theme doing things differently.

Any thoughts?

pdewouters commented 10 years ago

@mattheu so if a theme or plugin has a Gruntfile with different tasks, it isn't an issue? They can coexist? If so, then yeah

mattheu commented 10 years ago

Yes they can co-exist.

joehoyle commented 10 years ago

I am happy for this to go in, @mattheu feel free to merge if you don't see any outstanding todos.